David Smiley created SOLR-12420:
-----------------------------------
Summary: Propose removing schema version; use luceneMatchVersion
instead
Key: SOLR-12420
URL: https://issues.apache.org/jira/browse/SOLR-12420
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: David Smiley
I propose that the schema version be removed in lieu of using
luceneMatchVersion for this. One less thing to manage (in code, need REST API
-- SOLR-7242, thing to document; etc.). We don't need the fidelity to
differentiate from luceneMatchVersion. We're already using luceneMatchVersion
for things instead of having a ton of additional version numbers. I can
understand the point of putting a version number in in a config file but I
don't think we should continue this practice.
To make this happen, if the luceneMatchVersion is >= 7.4 (the release which we
start doing this) then a non-existent schema version becomes equivalent to the
latest schema version. Specifying the schema version becomes deprecated but
supported; we might log a warning.
In 8.0, strip schema version out altogether.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
