# How to change the stop words list for the TwitterRiver index **URL:** \ **Category:** Elasticsearch\ **Created:** [March 4, 2012, 2:36pm UTC](https://discuss.elastic.co/t/how-to-change-the-stop-words-list-for-the-twitterriver-index/6879 "2012-03-04T14:36:16Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![benq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benq/32/1428_2.png) [@benq](https://discuss.elastic.co/u/benq)\ **Post date:** [March 4, 2012, 2:36pm UTC](https://discuss.elastic.co/t/how-to-change-the-stop-words-list-for-the-twitterriver-index/6879/1 "2012-03-04T14:36:16Z")
Hi, I am using the TwitterRiver with 0.19. How can I change the stopwords list ? From the documentation, I should be able to provide a custom word list either at index creation, which is not convenient because the index is automatically created by the TwitterRiver (and I would prefer not to touch this code) or in my yaml.xml. Is there a third possibility, like updating the index definition after its creation? I tried to configure the standard analyser to use my external stopwords file by adding: index.analysis.analyser.standard.stopwords\_path: "extendedstopwords\_en.txt" without success. How should I do that? benq ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [March 4, 2012, 4:24pm UTC](https://discuss.elastic.co/t/how-to-change-the-stop-words-list-for-the-twitterriver-index/6879/2 "2012-03-04T16:24:04Z")
You can configure the standard analyzer globally by adding the following settings to elasticsearch.yml index: analysis: analyzer: default: type: standard stopwords\_path: "extendedstopwords\_en.txt" You will have to restart the node for settings to take effect after you change node's config file. On Sunday, March 4, 2012 9:36:16 AM UTC-5, benq wrote: > Hi, > > I am using the TwitterRiver with 0.19. > > How can I change the stopwords list ? > > From the documentation, I should be able to provide a custom word list > either at index creation, which is not convenient because the index is > automatically created by the TwitterRiver (and I would prefer not to > touch this code) or in my yaml.xml. Is there a third possibility, like > updating the index definition after its creation? > > I tried to configure the standard analyser to use my external > stopwords file by adding: > index.analysis.analyser.standard.stopwords\_path: > "extendedstopwords\_en.txt" > without success. > > How should I do that? > > benq ---
**Author:** ![benq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benq/32/1428_2.png) [@benq](https://discuss.elastic.co/u/benq)\ **Post date:** [April 24, 2012, 12:17pm UTC](https://discuss.elastic.co/t/how-to-change-the-stop-words-list-for-the-twitterriver-index/6879/3 "2012-04-24T12:17:20Z")
How can I update the stop work list without restarting ES (and interrupting the indexing)? Is that possible? Le dimanche 4 mars 2012 17:24:04 UTC+1, Igor Motov a écrit : > You can configure the standard analyzer globally by adding the following > settings to elasticsearch.yml > > index: > analysis: > analyzer: > default: > type: standard > stopwords\_path: "extendedstopwords\_en.txt" > > You will have to restart the node for settings to take effect after you > change node's config file. > > On Sunday, March 4, 2012 9:36:16 AM UTC-5, benq wrote: > > > Hi, > > > > I am using the TwitterRiver with 0.19. > > > > How can I change the stopwords list ? > > > > From the documentation, I should be able to provide a custom word list > > either at index creation, which is not convenient because the index is > > automatically created by the TwitterRiver (and I would prefer not to > > touch this code) or in my yaml.xml. Is there a third possibility, like > > updating the index definition after its creation? > > > > I tried to configure the standard analyser to use my external > > stopwords file by adding: > > index.analysis.analyser.standard.stopwords\_path: > > "extendedstopwords\_en.txt" > > without success. > > > > How should I do that? > > > > benq ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [April 24, 2012, 1:31pm UTC](https://discuss.elastic.co/t/how-to-change-the-stop-words-list-for-the-twitterriver-index/6879/4 "2012-04-24T13:31:11Z")
You can update the stop word list without restarting ES by closing and opening the index. This will, however, interrupt the indexing. Alternatively, you can try rolling restart of entire cluster, but this might lead to inconsistency between nodes on the top of expected inconsistencies that would result from changing the analyzer without reindexing. On Tuesday, April 24, 2012 8:17:20 AM UTC-4, benq wrote: > How can I update the stop work list without restarting ES (and > interrupting the indexing)? > Is that possible? > > Le dimanche 4 mars 2012 17:24:04 UTC+1, Igor Motov a écrit : > > > You can configure the standard analyzer globally by adding the following > > settings to elasticsearch.yml > > > > index: > > analysis: > > analyzer: > > default: > > type: standard > > stopwords\_path: "extendedstopwords\_en.txt" > > > > You will have to restart the node for settings to take effect after you > > change node's config file. > > > > On Sunday, March 4, 2012 9:36:16 AM UTC-5, benq wrote: > > > > > Hi, > > > > > > I am using the TwitterRiver with 0.19. > > > > > > How can I change the stopwords list ? > > > > > > From the documentation, I should be able to provide a custom word list > > > either at index creation, which is not convenient because the index is > > > automatically created by the TwitterRiver (and I would prefer not to > > > touch this code) or in my yaml.xml. Is there a third possibility, like > > > updating the index definition after its creation? > > > > > > I tried to configure the standard analyser to use my external > > > stopwords file by adding: > > > index.analysis.analyser.standard.stopwords\_path: > > > "extendedstopwords\_en.txt" > > > without success. > > > > > > How should I do that? > > > > > > benq ---
**Author:** ![benq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benq/32/1428_2.png) [@benq](https://discuss.elastic.co/u/benq)\ **Post date:** [April 26, 2012, 12:25pm UTC](https://discuss.elastic.co/t/how-to-change-the-stop-words-list-for-the-twitterriver-index/6879/5 "2012-04-26T12:25:09Z")
So, there is no way to do an "hot update" of the stop words list?! It would be great to have the stopwords list stored as an ES document... Le mardi 24 avril 2012 15:31:11 UTC+2, Igor Motov a écrit : > You can update the stop word list without restarting ES by closing and > opening the index. This will, however, interrupt the indexing. > Alternatively, you can try rolling restart of entire cluster, but this > might lead to inconsistency between nodes on the top of > expected inconsistencies that would result from changing the analyzer > without reindexing. > > On Tuesday, April 24, 2012 8:17:20 AM UTC-4, benq wrote: > > > How can I update the stop work list without restarting ES (and > > interrupting the indexing)? > > Is that possible? > > > > Le dimanche 4 mars 2012 17:24:04 UTC+1, Igor Motov a écrit : > > > > > You can configure the standard analyzer globally by adding the following > > > settings to elasticsearch.yml > > > > > > index: > > > analysis: > > > analyzer: > > > default: > > > type: standard > > > stopwords\_path: "extendedstopwords\_en.txt" > > > > > > You will have to restart the node for settings to take effect after you > > > change node's config file. > > > > > > On Sunday, March 4, 2012 9:36:16 AM UTC-5, benq wrote: > > > > > > > Hi, > > > > > > > > I am using the TwitterRiver with 0.19. > > > > > > > > How can I change the stopwords list ? > > > > > > > > From the documentation, I should be able to provide a custom word list > > > > either at index creation, which is not convenient because the index is > > > > automatically created by the TwitterRiver (and I would prefer not to > > > > touch this code) or in my yaml.xml. Is there a third possibility, like > > > > updating the index definition after its creation? > > > > > > > > I tried to configure the standard analyser to use my external > > > > stopwords file by adding: > > > > index.analysis.analyser.standard.stopwords\_path: > > > > "extendedstopwords\_en.txt" > > > > without success. > > > > > > > > How should I do that? > > > > > > > > benq ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:31am UTC](https://discuss.elastic.co/t/how-to-change-the-stop-words-list-for-the-twitterriver-index/6879/6 "2017-07-06T03:31:03Z")