On 5/24/2017 1:44 AM, Adrien Grand wrote: > We said before that we could move it to the solr sub-folder so that > Solr can support them for one additional major release (it can be done > on top of Lucene, doesn't need to be supported in Lucene directly). > However it is probably important to do whatever needs to be done now > (ie. before 7.0 is released) so that the removal of legacy numerics > will be seamless for users in 8.0. For instance maybe Solr should > disallow the addition of legacy numerics to the schema of indices that > are created on 7.x? Or alternatively implicitly upgrade those fields > to points (for 7.x indices only, otherwise it would break old indices) > if you think it provides a better user experience.
Moving the legacy numeric support to Solr for 7.x might be the way to go. I would prefer to have it remain in Lucene for another major version, but I suspect there will be resistance. I think that ES users could also benefit from legacy support remaining in Lucene for a while longer. I don't know how Solr would distinguish between existing legacy numeric fields and fields that are added later, so I'm not sure there's anything we could do to prevent users from setting up a schema that can't be used later. > To me the best trade-off is to stop doing 6.x minor releases once 7.0 > is out. I did say it would be relatively safe to do bugfixes and backport self-contained features in 6.x after 7.0 comes out as long as care is taken to not change the index format or analysis component behavior. Despite saying that, I actually agree with you that new minor releases (and therefore new features) should be avoided in the previous major version unless there is a VERY compelling reason. It doesn't seem very likely that a compelling reason will be encountered. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
