[ 
https://issues.apache.org/jira/browse/SOLR-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343557#comment-17343557
 ] 

David Smiley commented on SOLR-12420:
-------------------------------------

The essence of what I want most is to eliminate the need for a version specific 
to the schema file.  If we are to have any configuration version at all for 
Solr configuration (debatable!), then one is enough to govern the whole 
configSet: solrconfig.xml + schema.xml + anything else  next to it like 
elevate.xml etc.  I argue this is easier to maintain, and sufficient.  If we 
are to have a Solr wide configuration variable, then we might call this a 
"solrCompatVersion" or some-such.

luceneMatchVersion is about tokenization compatibility of the index, and only a 
handful of Lucene level things react to this setting.

> 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
>            Assignee: David Smiley
>            Priority: Major
>             Fix For: main (9.0)
>
>
> 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.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to