Re: Dealing with index format changes

2017-01-29 Thread Uwe Schindler
As far as I remember, this is a Luke related display bug (the nulls in output on position increments greater than 1). The phrase query question is unrelated to the display bug. This is documented in the migration guide. The problem is that old indexes can't play with new phrase query and query

Re: Dealing with index format changes

2017-01-29 Thread Adrien Grand
Hi Chris, this "null_1" token is unexpected to me. Did you reindex with Lucene 4.10.3 or just upgrade to the new file format using merging? Can you also share your analysis chain? Le sam. 28 janv. 2017 à 12:22, Chris Bamford a écrit : > Hello > > I am in the process of moving from indexing with

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