You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2016/11/16 15:21:58 UTC

[jira] [Created] (SOLR-9778) improve luceneMatchVersion handling

David Smiley created SOLR-9778:
----------------------------------

             Summary: improve luceneMatchVersion handling
                 Key: SOLR-9778
                 URL: https://issues.apache.org/jira/browse/SOLR-9778
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: David Smiley


I was thinking about luceneMatchVersion and how it's annoying to both explain and get right, and maintain.  I think there's a way in Solr we can do this way better:

When an index is initialized, record the luceneMatchVersion in effect into a file in the data directory, like luceneMatchVersion.txt.  It's a file that will never be modified.

The luceneMatchVersion in effect is the first of these that are specified:
* {{<luceneMatchVersion>}} in solrconfig.xml
* data/luceneMatchVersion.txt 
* {{org.apache.lucene.util.Version.LATEST}}

With this approach, we can eliminate putting {{<luceneMatchVersion>}} into solrconfig.xml by default.  Most users will have no need to bother setting it, even during an upgrade of either an existing index, or when they re-index.  Of course there are cases where the user knows what they are doing and insists on a different luceneMatchVersion, and they can specify that still.

Perhaps instead of a new file (data/luceneMatchVersion.txt), it might go into core.properties.  I dunno.

_(disclaimer: as I write this, I have no plans to work on this at the moment)_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org