Cassandra Targett created SOLR-11762:
----------------------------------------
Summary: Default solrconfig.xml for .system collection uses LATEST
for luceneMatchVersion
Key: SOLR-11762
URL: https://issues.apache.org/jira/browse/SOLR-11762
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: blobstore
Reporter: Cassandra Targett
Priority: Minor
I noticed a WARN error in my Solr logs after enabling the .system collection:
{code}
WARN - 2017-12-14 15:29:55.025; [ ] org.apache.solr.core.Config; You should
not use LATEST as luceneMatchVersion property: if you use this setting, and
then Solr upgrades to a newer release of Lucene, sizable changes may happen. If
precise back compatibility is important then you should instead explicitly
specify an actual Lucene version.
{code}
I traced this back to the default {{solrconfig.xml}} for the .system
collection, which comes from
{{solr/core/src/resources/SystemCollectionSolrConfig.xml}} and sets the
{{luceneMatchVersion}} to "LATEST" at line 3.
I can't think of a specific case where this has caused a problem, but if we're
warning for it we know it's at least theoretically possible that it could cause
a problem in the future. Plus it's a poor user experience to do something by
default that causes WARN errors that could cause confusion that something is
mis-configured.
The {{addVersion.py}} script could be modified to include updating this file
when it's run as part of the release process. Then users wouldn't see this
warning and we would avoid unintentional trouble in the future.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
