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

David Smiley commented on SOLR-9778:
------------------------------------

bq. Maybe put a new file into conf?

If it were initialized at the time a configSet is first used, then I think that 
might be okay.  It could interfere with configSet sharing and read-only 
configSets though.  My main concern with conf for this purpose is semantics; I 
don't view this as configuration; it's metadata for the index.  You shouldn't 
go in and change this file; you would instead edit the config to override it.  
But few would have a desire to do that, I think.

> Make luceneMatchVersion handling easy/automatic
> -----------------------------------------------
>
>                 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to