Update on synonyms file requires full index recreation?

Elastic Stack Elasticsearch
1

Hi,

ES 1.1.1
when i use the synonyms filter with a synonyms_path file i have to create
whole index again to take new synonyms in effect.
It is not enough to update the index data, in need to remove, create and
update whole index.

Is that expected behaviour? If so what is ur strategy to get this done on a
productive system?

Thx & regards
Tom

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0d8448bb-92e2-4748-a624-29fd95ea4ba1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Read about file wathcer service
here Analysis Synonym: Shared on node level + auto reload from file system · Issue #4063 · elastic/elasticsearch · GitHub

Anything happening according this or am i monitoring the wrong path?

Am Freitag, 16. Mai 2014 13:42:19 UTC+2 schrieb Tom:

Hi,

ES 1.1.1
when i use the synonyms filter with a synonyms_path file i have to create
whole index again to take new synonyms in effect.
It is not enough to update the index data, in need to remove, create and
update whole index.

Is that expected behaviour? If so what is ur strategy to get this done on
a productive system?

Thx & regards
Tom

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c9eb7ca7-328b-4829-b636-3a69f714f226%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

The synonym file will be read whenever a new index is created or if an
index is re-opened. Closing and opening an index is not the cleanest
solution, so I created a plugin to help solve the problem:
https://github.com/brusic/refresh-token-filters

However, this version of the plugin does not seem to be working 100%.
Unfortunately, I do not have time to test. I have a different version of
the plugin working at my company for over a year without any issues. It has
more bells and whistles (connects to a database for the term lists, timed
refreshes), but I wanted my public version to be simpler. The most
important change is that I moved from tracking the filter Java objects
directly to using the IndicesService. However, I found that some analyzers
can be cached and therefore there internal filters do not change. Like I
said, I don't have time to test, but I am assuming that is the issue.

Cheers,

Ivan

On Fri, May 16, 2014 at 3:19 PM, Tom t.oppelt@superreal.de wrote:

Read about file wathcer service here
Analysis Synonym: Shared on node level + auto reload from file system · Issue #4063 · elastic/elasticsearch · GitHub

Anything happening according this or am i monitoring the wrong path?

Am Freitag, 16. Mai 2014 13:42:19 UTC+2 schrieb Tom:

Hi,

ES 1.1.1
when i use the synonyms filter with a synonyms_path file i have to create
whole index again to take new synonyms in effect.
It is not enough to update the index data, in need to remove, create and
update whole index.

Is that expected behaviour? If so what is ur strategy to get this done on
a productive system?

Thx & regards
Tom

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/c9eb7ca7-328b-4829-b636-3a69f714f226%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/c9eb7ca7-328b-4829-b636-3a69f714f226%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDub2OH1CKS1phM286gC7808vqGVXyJDtf7D%3DfoyBb5%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.