Varun Thacker created SOLR-12501:
------------------------------------
Summary: System Collection should use the correct
luceneMatchVersion
Key: SOLR-12501
URL: https://issues.apache.org/jira/browse/SOLR-12501
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Varun Thacker
Whenever we create the system collection, the solrconfig is hard-coded and
comes from SystemCollectionSolrConfig.java
Here we always set the luceneMatchVersion to the latest instead of the lucene
version that is being released.
When you go to create the collection we will get this warning the logs
{code:java}
WARN - 2018-06-19 14:53:00.400; [c:.system s:shard1 r:core_node2
x:.system_shard1_replica_n1] 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}
The downside is if a user upgrades Solr then the new docs analysis behaviour
could differ.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
