I can at least answer the second question. Lucene guarantees backwards read compatibility for _one_ major revision. 6x can read 5x indexes, but not 4x.
The back-compat logic is difficult enough for one major revision, so when Lucene moves to a new major version the classes supporting version-2 are removed. Best, Erick On Sun, Jun 19, 2016 at 8:51 PM, Issei Nishigata <duo.2...@gmail.com> wrote: > Hi, all. > > I am using Solr5.5. > > I am planning to activate "enablePositionIncrements" by customizing > "XXXFilterFactory" in order to make autoGeneratedPhraseQueries work > properly. > Can anyone tell me about the impact of such customizing? > > I am planning two kinds of customizing mentioned below. > - To allow schema.xml to specify "enbalePositionIncrements". > - To make "lucene43XXXFilter" is called in case of > "enablePositionIncrements=false". > > I would appreciate if you can tell me the reason "enablePostionIncrements" > is deprecated after Solr4.4 in the first place. > And, I also appreciate why "lucene43XXXFilter" is completely removed in > Solr6. > > > Thanks, > Issei
