Can we see a full stack trace for that IllegalArgumentException? AFAIk, enablePositionIncrements=false is deprecated in 4.x but not removed. It will be removed in 5.0 though.
On Fri, Sep 13, 2013 at 3:34 AM, Christopher Condit <con...@sdsc.edu> wrote: > While attempting to upgrade from Solr 4.3.0 to Solr 4.4.0 I ran into > this exception: > > java.lang.IllegalArgumentException: enablePositionIncrements=false is > not supported anymore as of Lucene 4.4 as it can create broken token > streams > > which led me to https://issues.apache.org/jira/browse/LUCENE-4963. I > need to be able to match queries irrespective of intervening stopwords > (which used to work with enablePositionIncrements="true"). For > instance: "foo of the bar" would find documents matching "foo bar", > "foo of bar", and "foo of the bar". With this option deprecated in > 4.4.0 I'm not clear on how to maintain the same functionality. > > The package javadoc adds: > > If the selected analyzer filters the stop words "is" and "the", then > for a document containing the string "blue is the sky", only the > tokens "blue", "sky" are indexed, with position("sky") = 3 + > position("blue"). Now, a phrase query "blue is the sky" would find > that document, because the same analyzer filters the same stop words > from that query. But the phrase query "blue sky" would not find that > document because the position increment between "blue" and "sky" is > only 1. > > If this behavior does not fit the application needs, the query parser > needs to be configured to not take position increments into account > when generating phrase queries. > > But there's no mention of how to actually configure the query parser > to do this. Does anyone know how to deal with this issue as Solr moves > toward 5.0? > > Crossposted from stackoverflow: > http://stackoverflow.com/questions/18668376/solr-4-4-stopfilterfactory-and-enablepositionincrements -- Regards, Shalin Shekhar Mangar.
