Good question Ilan,
I think the Solr project needs to state (and write down) some principles for
how and when to upgrade Lucene.
We should obviously not upgrade to a new major lucene version in a minor Solr
release, so it feels natural that Solr N+1 most often (but not necessarily)
also contain
Do we risk not being able to support the Solr N-1 indexes in Solr N (i.e.
no easy migration path) if between Solr N-1 and Solr N Lucene has advanced
from P to P+2 and P+2 does not support indexes in P format?
On Fri, May 7, 2021 at 12:23 AM David Smiley wrote:
> Thanks for raising this. I'm not
Thanks for raising this. I'm not aware of WIP.
I think we can create a "SolrVersion" class, copying the approach Lucene
has taken? The SolrVersion can have access to the Lucene Version, since
Solr is dependent on Lucene.
Another related issue is that I think Solr should do away with the schema
Hi,
So far Solr has always had the same version as Lucene, so we have tons of
places in our code that checks the org.apache.lucene.util.Version class.
Going forward we'll soon end up in a situation where we e.g. release Solr x on
top of Lucene y.
Some places we ne need to continue checking on L
