Shinsuke Sugaya
Shinsuke Sugaya
ElasticsearchClusterRunner is invoked from inside your Java application. Java settings specified at your application are applied to elasticsearch. So, jvm.options file is not needed.
Check "b-bit minhash" on Google.
Our plugin sets transport.tcp.port to specific port(9301-9303) for 3 nodes, but standalone elasticsearch uses 9300-9400(range). I think it's difficult to change the default value of our plugin because the plugin...
Did you add nori?
How did you send the mappings.json?
Could you provide information to reproduce it?
It's for an index setting, not mapping. ``` final String indexSettings = "{\n" + " \"properties\": {\n" + " \"hahahoho\": {\n" + " \"type\": \"keyword\"\n" + " }\n" + "...
It seems that elasticsearch does not recognize minhash filter. The sample setting is [here](https://github.com/codelibs/fess/blob/fess-13.9.1/src/main/resources/fess_indices/fess.json#L647-L652).
> "minhash_analyzer":"minhash_analyzerhg" Typo...
minhash_value depends on a tokenizer for minhash_analyzer.