ErickErickson commented on issue #824: LUCENE-8755: QuadPrefixTree robustness URL: https://github.com/apache/lucene-solr/pull/824#issuecomment-519489983 No, IndexUpgraderTool doesn’t really help. It rewrites the index in the current format, but does not (and cannot) make it look just as though the index had been indexed from scratch. From Robert Muir: “I think the key issue here is Lucene is an index not a database. Because it is a lossy index and does not retain all of the user's data, its not possible to safely migrate some things automagically. In the norms case IndexWriter needs to re-analyze the text ("re-index") and compute stats to get back the value, so it can be re-encoded. The function is y = f(x) and if x is not available its not possible, so lucene can't do it.” So Lucene will work with X-1, but not version X-2. As of 8.0, it will refuse to even open an index that has ever been touched by Solr 6x or earlier, regardless of running IndexUpgraderTool etc. Best, Erick > On Aug 8, 2019, at 12:55 AM, 鹿の遠音 <notificati...@github.com> wrote: > > I find that Lucene has a tool called IndexUpgrader. Maybe updating index is a better solution for backward compatibility? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. >
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
