Le jeu. 26 janv. 2017 à 20:52, Shawn Heisey <apa...@elyograg.org> a écrit :
The fast deprecation of the legacy numeric types has strong potential to
impact a very large number of people who use older versions of *any*
software based on Lucene, including Elasticsearch and Solr. If their
current configuration uses the legacy types, they will be unable to
upgrade to software using Lucene 7.0 and keep using their existing indexes.
I don't think this statement is accurate. Why would it affect Lucene users
if they started using points for new indices when they upgraded to Lucene 6?
There are two cases: either their current configuration uses points, which
means the index was created with Lucene 6.0+, which will be fine with
Lucene 7. Or the index uses legacy numerics, but that means the index was
created with Lucene 5 so Lucene 7 cannot read it anyway.
I know some users use merging to upgrade their index from the N-2 file
format to the N-1 file format and then to the N file format, but this is
dangerous as it relies on backward compatibility with version N-2 of
everything that is performed on top of the file formats like the legacy
numerics, but also analysis, ...