On 10/24/2017 9:38 AM, Markus Jelsma wrote: > We have switched back to 6.6 for now so we are fine for now. Although i > didn't try range queries other than date, i assume other Point fields can > also have this problem? > > That would mean completely switch back to Trie if you don't can/want to fully > reindex all data. > > Suggestions? A forceMerge at least fixes nothing. I'll take a look at index > upgrade tool.
As I said in the earlier reply, data written by a Trie field class cannot be read by a Point field class. That's true for any of them -- Int, Float, Double, Long, etc. Lucene's IndexUpgrader just performs a forceMerge on the index. There's nothing special about the job it does. It is not capable of converting one field class to another. It doesn't know anything about Solr's field classes. Solr 7.x can still use Trie fields, but they will be gone by the 8.0 release. Lucene 7.0 no longer contains the legacy numeric classes that Trie fields are built with. Solr has kept those around for one more major version. Thanks, Shawn
