[
https://issues.apache.org/jira/browse/SOLR-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-12420.
---------------------------------
Fix Version/s: (was: main (10.0))
Resolution: Won't Fix
I agree with Hossman; the schema is an important file and ideally it has a
version stamped into it. We should even require it (warning) since the default
is 1.0 (wow). Even the XML processing instruction has a version.
> Propose removing schema version; use luceneMatchVersion instead
> ---------------------------------------------------------------
>
> Key: SOLR-12420
> URL: https://issues.apache.org/jira/browse/SOLR-12420
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Priority: Blocker
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
