atom feed19 messages in org.apache.lucene.solr-devRe: Lucene/Solr 7
FromSent OnAttachments
Adrien GrandJan 24, 2017 8:52 am 
Ishan ChattopadhyayaJan 24, 2017 9:16 am 
Joel BernsteinJan 24, 2017 9:28 am 
Michael McCandlessJan 24, 2017 9:43 am 
Joel BernsteinJan 24, 2017 10:02 am 
Tommaso TeofiliJan 24, 2017 10:09 am 
Michael McCandlessJan 24, 2017 11:01 am 
David SmileyJan 24, 2017 8:09 pm 
Uwe SchindlerJan 25, 2017 2:29 am 
Christine Poerschke (BLOOMBERG/ LONDON)Jan 25, 2017 2:38 am 
Ramkumar R. AiyengarJan 25, 2017 4:50 am 
Tomás Fernández LöbbeJan 25, 2017 9:36 am 
Anshum GuptaJan 25, 2017 1:21 pm 
Shawn HeiseyJan 26, 2017 11:51 am 
Ishan ChattopadhyayaJan 26, 2017 1:08 pm 
Adrien GrandJan 26, 2017 1:09 pm 
Adrien GrandJan 26, 2017 1:40 pm 
Shawn HeiseyJan 26, 2017 4:48 pm 
Tomás Fernández LöbbeJan 26, 2017 5:17 pm 
Subject:Re: Lucene/Solr 7
From:Adrien Grand (jpou@gmail.com)
Date:Jan 26, 2017 1:40:43 pm
List:org.apache.lucene.solr-dev

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, ...