At the moment i have a default analyser configured for my whole
cluster. My config/elasticsearch.json looks like this:
However I want to use this default analyser for an index called
'content' only. I know i can set this up by doing a put directly at
localhost:9200/content/ via curl, but I like to keep my default config
file up to date in case I ever need to recreate everything from
scratch its set up automatically.
Can anyone give me any pointers on how i could adjust the config
listed above to work for the 'content' index only?
However I want to use this default analyser for an index called
'content' only. I know i can set this up by doing a put directly at
localhost:9200/content/ via curl, but I like to keep my default config
file up to date in case I ever need to recreate everything from
scratch its set up automatically.
Can anyone give me any pointers on how i could adjust the config
listed above to work for the 'content' index only?
What i'd like to do is have the indexer stored in a configuration file
so that if i delete all my indexes and recreate the 'content' index it
is automatically applied - in the same manner that i have mappings for
various different types stored as json files in the config/mapping
directory
However I want to use this default analyser for an index called
'content' only. I know i can set this up by doing a put directly at
localhost:9200/content/ via curl, but I like to keep my default config
file up to date in case I ever need to recreate everything from
scratch its set up automatically.
Can anyone give me any pointers on how i could adjust the config
listed above to work for the 'content' index only?
There isn't a way to associate a specific settings with an index (as you can with mappings). It was raised several times, but I don't think an issue was opened to implement it.
On Wednesday, February 8, 2012 at 4:17 PM, WeeJames wrote:
I know I can put it in via the API.
What i'd like to do is have the indexer stored in a configuration file
so that if i delete all my indexes and recreate the 'content' index it
is automatically applied - in the same manner that i have mappings for
various different types stored as json files in the config/mapping
directory
However I want to use this default analyser for an index called
'content' only. I know i can set this up by doing a put directly at
localhost:9200/content/ via curl, but I like to keep my default config
file up to date in case I ever need to recreate everything from
scratch its set up automatically.
Can anyone give me any pointers on how i could adjust the config
listed above to work for the 'content' index only?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.