# Enable Position Increments property not available **URL:** \ **Category:** Elasticsearch\ **Created:** [February 5, 2014, 6:49pm UTC](https://discuss.elastic.co/t/enable-position-increments-property-not-available/15627 "2014-02-05T18:49:36Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Christian\_Rohling](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_rohling/32/709_2.png) [@Christian\_Rohling](https://discuss.elastic.co/u/Christian_Rohling)\ **Post date:** [February 5, 2014, 6:49pm UTC](https://discuss.elastic.co/t/enable-position-increments-property-not-available/15627/1 "2014-02-05T18:49:36Z")
Hello, I am trying to use the shingle token filter, and previously was using a stop-filter with the enable\_position\_increments property([http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html)). This property was removed in 0.90.3 according to the documentation, and I was wondering if there was another method to achieve the same functionality? I currently can see unwanted characters in my facets, and need to make sure that only expected results appear. Thanks, Christian Rohling -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e83b7f44-44f1-4cf9-9efb-1cf823cc5ecf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e83b7f44-44f1-4cf9-9efb-1cf823cc5ecf%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![polyfractal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polyfractal/32/48162_2.png) [@polyfractal](https://discuss.elastic.co/u/polyfractal)\ **Post date:** [February 6, 2014, 2:38pm UTC](https://discuss.elastic.co/t/enable-position-increments-property-not-available/15627/2 "2014-02-06T14:38:27Z")
Hi Christian, I looked into the issue and it appears there isn't really an alternative at the moment. The property was removed because Lucene removed the underlying functionality, since it can potentially break token streams (usually in regards to synonyms). You can see the issue here: [[LUCENE-4065] FilteringTokenFilter should never corrupt the tokenstream graph - ASF JIRA](https://issues.apache.org/jira/browse/LUCENE-4065) When I've used the parameter before, it was to remove underscores that were generated due to a stop-word filter. If that's your case, you might consider adding a pattern-replace filter to remove lone underscores. This is admittedly a terrible hack, but it might work until Lucene sorts out the underlying issue. Sorry I don't have better news ☹ -Zach On Wednesday, February 5, 2014 1:49:36 PM UTC-5, Christian Rohling wrote: > Hello, > I am trying to use the shingle token filter, and previously was using > a stop-filter with the enable\_position\_increments property( > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html)). > This property was removed in 0.90.3 according to the documentation, and I > was wondering if there was another method to achieve the same > functionality? I currently can see unwanted characters in my facets, and > need to make sure that only expected results appear. > > Thanks, > Christian Rohling -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7e43170c-bf21-4df8-a1a2-186c05c8ae7d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7e43170c-bf21-4df8-a1a2-186c05c8ae7d%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Andreas\_Loupasakis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andreas_loupasakis/32/1184_2.png) [@Andreas\_Loupasakis](https://discuss.elastic.co/u/Andreas_Loupasakis)\ **Post date:** [October 16, 2014, 3:30pm UTC](https://discuss.elastic.co/t/enable-position-increments-property-not-available/15627/3 "2014-10-16T15:30:06Z")
Is there any progress on this issue? On Thursday, February 6, 2014 4:38:27 PM UTC+2, Zachary Tong wrote: > Hi Christian, I looked into the issue and it appears there isn't really an > alternative at the moment. The property was removed because Lucene removed > the underlying functionality, since it can potentially break token streams > (usually in regards to synonyms). You can see the issue here: > [[LUCENE-4065] FilteringTokenFilter should never corrupt the tokenstream graph - ASF JIRA](https://issues.apache.org/jira/browse/LUCENE-4065) > > When I've used the parameter before, it was to remove underscores that > were generated due to a stop-word filter. If that's your case, you might > consider adding a pattern-replace filter to remove lone underscores. This > is admittedly a terrible hack, but it might work until Lucene sorts out the > underlying issue. > > Sorry I don't have better news ☹ > -Zach > > On Wednesday, February 5, 2014 1:49:36 PM UTC-5, Christian Rohling wrote: > > > Hello, > > I am trying to use the shingle token filter, and previously was using > > a stop-filter with the enable\_position\_increments property( > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-stop-tokenfilter.html)). > > This property was removed in 0.90.3 according to the documentation, and I > > was wondering if there was another method to achieve the same > > functionality? I currently can see unwanted characters in my facets, and > > need to make sure that only expected results appear. > > > > Thanks, > > Christian Rohling -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/3f5f7d5a-be36-4f20-8c0e-88a771559fc3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3f5f7d5a-be36-4f20-8c0e-88a771559fc3%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:55am UTC](https://discuss.elastic.co/t/enable-position-increments-property-not-available/15627/4 "2017-07-06T00:55:46Z")