Overriding configuration by API

Hi,

We have configured the analyzer settings for our ES node from the elasticsearch.yml. This works perfectly for us, since we had hardly any changes.
Starting today we are using a lot of synonyms, which we want to be more flexible with. I can succesfully set the synonym settings using the _settings api endpoint. However, when removing settings in the update, it doesn't work. Consider the following example: https://gist.github.com/jappievw/f6ea0d7ace1df2201a70. I performed the following steps:
Create a new index called "test".
Update settings with contents of the test index with the contents of initial-settings.json
The update is successfully applied, see settings-after-initial.json
Now remove the second defined synonym of the index by updating the index "test" settings, with an updated config: settings-update.json
The result after update is settings-after-update.json. The second synonym hasn't been removed.

I expected the second synonym to be removed. Few questions about this:
Did I miss something in the documentation about removing configuration settings?
Is it possible to update the settings at once for an index?
How do others manage synonyms?

Thanks for your help,

Jasper

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hiya

We have configured the analyzer settings for our ES node from the
elasticsearch.yml. This works perfectly for us, since we had hardly
any changes.
Starting today we are using a lot of synonyms, which we want to be
more flexible with. I can succesfully set the synonym settings using
the _settings api endpoint. However, when removing settings in the
update, it doesn't work. Consider the following example:
https://gist.github.com/jappievw/f6ea0d7ace1df2201a70. I

Updating analysis settings is tricky to say the least. Generally
changes are rejected.

One possibility is to store your synonyms in a file (which needs to be
available on every node), then you can update the file (again on every
node), close and reopen the index, and your synonyms list will have
changed.

clint

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Thanks for your reply Clinton. Luckily we use puppet for the distrubution
of the configuration files.
There is no way to open and close all indices at once, right? That would
make automation of these changes a breeze.

Thanks, Jasper

On Wednesday, February 13, 2013 11:40:18 AM UTC+1, Clinton Gormley wrote:

Hiya

We have configured the analyzer settings for our ES node from the
elasticsearch.yml. This works perfectly for us, since we had hardly
any changes.
Starting today we are using a lot of synonyms, which we want to be
more flexible with. I can succesfully set the synonym settings using
the _settings api endpoint. However, when removing settings in the
update, it doesn't work. Consider the following example:
https://gist.github.com/jappievw/f6ea0d7ace1df2201a70. I

Updating analysis settings is tricky to say the least. Generally
changes are rejected.

One possibility is to store your synonyms in a file (which needs to be
available on every node), then you can update the file (again on every
node), close and reopen the index, and your synonyms list will have
changed.

clint

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Wed, 2013-02-13 at 04:37 -0800, Jasper van Wanrooy wrote:

Thanks for your reply Clinton. Luckily we use puppet for the
distrubution of the configuration files.
There is no way to open and close all indices at once, right? That
would make automation of these changes a breeze.

No, you have to close them by name. Also, reopening an index can be
time consuming as the index needs to be recovered from disk. I'd do a
flush before closing

clint

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No, you have to close them by name. Also, reopening an index can be
time consuming as the index needs to be recovered from disk. I'd do a
flush before closing

Ok, clear. Thanks for the explanation!

Jasper

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.