-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
In 5.0 LUCENE-4963 disallowed setting enablePositionIncrements=false on any token filter. The idea being no filter should change the token stream in a way that could mess up preceding or following analysis components
So if a user wants to be able to have PhraseQueries that match across stopwords they cannot unless the parser is configured to not take position increments into account when generating phrase queries .
This is documented in the "Token Position Increments" section here : https://lucene.apache.org/core/5_3_0/core/org/apache/lucene/analysis/package-summary.html
- relates to
-
LUCENE-4065 FilteringTokenFilter should never corrupt the tokenstream graph
-
- Open
-
-
SOLR-6468 Regression: StopFilterFactory doesn't work properly without deprecated enablePositionIncrements="false"
-
- Open
-
-
LUCENE-4963 Deprecate broken TokenFilter constructors
-
- Closed
-