I'm building a custom tokenizer in response to this: Performance of doc_values field vs analysed field None of this API appears to be documented (?), so I'm going off of code samples from other plugins/tokenizers, but when I restart elastic having deployed my tokenizer I get this error constantly i…

Just found one here: https://github.com/codelibs/elasticsearch-analysis-kuromoji-neologd/blob/2.3.x/src/main/java/org/codelibs/elasticsearch/kuromoji/neologd/index/analysis/KuromojiTokenizerFactory.java that has Environment in the constructor. Trying that!

What are you the entire contents of your tokenizer .java file (in particular, the imports)? Note that Tokenizers were change in 5.0 to be "deguiced", so they should no longer have these types of pains when developing.

Here are the entire contents of my TokenizerFactory class (sans package): import org.apache.lucene.analysis.Tokenizer; import org.elasticsearch.common.inject.Inject; import org.elasticsearch.common.inject.assistedinject.Assisted; import org.elasticsearch.common.settings.Settings; import org.elastic…

How are you starting elasticsearch?

sudo service elasticsearch restart

Sorry I don't have any other ideas. Guice is a nightmare, that is why we have been slowly removing it. You should really upgrade to 5.x :neutral_face:

Oh. :frowning: Any chance you could give me some guidance on how I might re-create the guice stuff to see why that's failing?

A shot in the dark, but are you sure that the IndexSettingsService is used in the constructor? Try using the index settings directly (which should be injected): public UrlTokenizerFactory(Index index, @IndexSettings Settings indexSettings, @Assisted String name, @Assisted Settings settings)

The guice stuff is all initialized in Node.java. At least, in there you can see which Module classes are loaded, which setup bindings in guice. It seems to find your class ok, but then does not find the constructor. Is the snippet you gave the entirety of your tokenizer factory class? I had first …

Thanks for your help. I tried your "shot in the dark". It compiled, and I got a slightly different error this time: Caused by: java.lang.IllegalStateException: [index.version.created] is not present in the index settings for index with uuid: [null] at org.elasticsearch.Version.indexCreated(Versio…

[image] Ivan: @IndexSettings Although this annotation doesn't resolve.

Building a custom tokenizer: "Could not find suitable constructor"

Elastic Stack Elasticsearch

system (system) Closed October 23, 2017, 2:19pm 17

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Error in custom provider, org.elasticsearch.common.inject.CreationException Elasticsearch	2	548	July 6, 2017
Error in custom provider, org.elasticsearch.common.inject.CreationException Elasticsearch	2	421	July 6, 2017
Custom Tokenizer won't uninstall Elasticsearch	8	2794	July 5, 2017
Integration Test : org.elasticsearch.common.inject.CreationException: Guice creation errors: Elasticsearch	1	546	July 2, 2018
CreateIndexRequestBuilder on 0.16.2 failed Elasticsearch	3	290	July 6, 2017

Building a custom tokenizer: "Could not find suitable constructor"

Related topics