Dealing with index format changes

2017-01-28 Thread Chris Bamford
Hello I am in the process of moving from indexing with 3.6.0 to 4.10.3 (albeit in 3.6.0 compatibility mode). Examination of the resulting indexes with Luke shows that text fields now contain null markers where stop words have been removed whereas the previous indexes had nothing: Indexed phrase

Re: Strange results returned from suggester

2017-01-28 Thread Michael McCandless
Hi Greg, OK StandardAnalyzer does indeed use StopFilter, with English stop words by default, which includes "will", so this explains what you are seeing. I suggest making your own analyzer just like StandardAnalyzer, except instead of StopFilter use the SuggestStopFilter class. That class was cr

Re: Strange results returned from suggester

2017-01-28 Thread Greg Huber
Michael, I am using the standard analyzer eith no stop words, and is build from an existing lucene index. org.apache.lucene.search.suggest.analyzing.AnalyzingInfixSuggester I am overriding the addContextToQuery to make it an AND rather than an OR public void addContextToQuery(Builder query, Byt