Error while creating index

[rbawaskar]

On running

node scripts/create_index.js


I am getting following error. I have elastic search installed and running properly.

[put mapping] pelias { [Error: RemoteTransportException[[White Queen][inet[/192.168.1.49:9300]][indices:admin/create]]; nested: IndexCreationException[[pelias] failed to create index]; nested: ElasticsearchIllegalArgumentException[failed to find analyzer type [pelias-analysis] or tokenizer for [plugin]]; nested: NoClassSettingsException[Failed to load class setting [type] with value [pelias-analysis]]; nested: ClassNotFoundException[org.elasticsearch.index.analysis.pelias-analysis.Pelias-analysisAnalyzerProvider]; ] message: 'RemoteTransportException[[White Queen][inet[/192.168.1.49:9300]][indices:admin/create]]; nested: IndexCreationException[[pelias] failed to create index]; nested: ElasticsearchIllegalArgumentException[failed to find analyzer type [pelias-analysis] or tokenizer for [plugin]]; nested: NoClassSettingsException[Failed to load class setting [type] with value [pelias-analysis]]; nested: ClassNotFoundException[org.elasticsearch.index.analysis.pelias-analysis.Pelias-analysisAnalyzerProvider]; ' } { error: 'RemoteTransportException[[White Queen][inet[/192.168.1.49:9300]][indices:admin/create]]; nested: IndexCreationException[[pelias] failed to create index]; nested: ElasticsearchIllegalArgumentException[failed to find analyzer type [pelias-analysis] or tokenizer for [plugin]]; nested: NoClassSettingsException[Failed to load class setting [type] with value [pelias-analysis]]; nested: ClassNotFoundException[org.elasticsearch.index.analysis.pelias-analysis.Pelias-analysisAnalyzerProvider]; ', status: 400 }

[rbawaskar]

tried with
Elastic Search version 1.4.2 and 1.3.4

[missinglink]

Hi @rbawaskar apologies for the poor documentation, this plugin needs to be installed first; which is why you are having issues, I will open a ticket to document that dependency better.

We're currently experiencing this issue with the plugin so I've assigned @hkrishna who is responsible for fixing the plugin and also ping @heffergm who may be able to provide information about the current status of the plugin and the correct install instructions which you can follow to avoid the above mentioned issue.

[heffergm]

You’ll want to use ES 1.3.4 and install the plugin via the following:

bin/plugin -url https://github.com/pelias/elasticsearch-plugin/blob/1.3.4/pelias-analysis.zip?raw=true -install pelias-analysis

Grant Heffernan

On Jan 6, 2015, at 8:33 AM, Peter Johnson a.k.a. insertcoffee notifications@github.com wrote:

Hi @rbawaskar https://github.com/rbawaskar apologies for the poor documentation, this plugin https://github.com/pelias/elasticsearch-plugin needs to be installed first; which is why you are having issues, I will open a ticket to document that dependency better.

We're currently experiencing this issue https://github.com/pelias/elasticsearch-plugin/issues/5 with the plugin so I've assigned @hkrishna https://github.com/hkrishna who is responsible for fixing the plugin and also ping @heffergm https://github.com/heffergm who may be able to provide information about the current status of the plugin and the correct install instructions which you can follow to avoid the above mentioned issue.

—
Reply to this email directly or view it on GitHub #34 (comment).

[rbawaskar]

@missinglink @heffergm Thanks guys for your support.
Installed the plugin.
Btw, one more question. (I am just starting to elasticsearch)
How do i add the analyzer to settings mapping ?

[rbawaskar]

Even after installing the plugin, I am getting same error. :(

[heffergm]

You restarted elasticsearch after installing the plugin?

Grant Heffernan

On Jan 6, 2015, at 10:36 AM, Ravindra Bawaskar notifications@github.com wrote:

Even after installing the plugin, I am getting same error. :(

—
Reply to this email directly or view it on GitHub #34 (comment).

[rbawaskar]

yes.

[heffergm]

Without being able to look at your environment it’s tough for me to say. The only reason you should see that error is if the plugin isn’t installed, so if you’re still getting it something isn’t set up correctly. You may want to take a look at the vagrant repository to build a test environment and get a handle on how things work.

Grant Heffernan

On Jan 6, 2015, at 10:37 AM, Ravindra Bawaskar notifications@github.com wrote:

yes.

—
Reply to this email directly or view it on GitHub #34 (comment).

[missinglink]

@rbawaskar can you please confirm that the plugin installs without issue? sometimes the install emits an error message which is hard to spot.

Trying to install it twice should emit an error that it is already installed.

Once the plugin has been installed it shows up for me here: http://localhost:9200/_cluster/stats?human=1&pretty=1

The last section of the json at that url has a property named 'plugins' inside which I have 'pelias-analysis' listed in my setup.

[missinglink]

re: your question about applying the plugin to an index, this is handled for you automatically if you use the default indeces (ie. if you use scripts/create_index.js)

The relevant parts are:
https://github.com/pelias/schema/blob/master/settings.js#L24 which should show up here: http://localhost:9200/_settings

once that has been defined and elasticsearch knows about the plugin, you can apply it on a per-field or per-index level like this: https://github.com/pelias/schema/blob/master/mappings/partial/suggest.json#L5

[rbawaskar]

@missinglink yes plugin shows up in stats. Thanks for the applying plugin to index part.

[missinglink]

ok cool, so is it working now? if not please post your error message again.

[rbawaskar]

@missinglink yes its working great now.
I was seeing plugin errors because there were multiple ES clusters on the network, and other clusters didn't had the plugin installed.

[jeannieh]

You might try the schema plugin as an alternative.