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

ASF subversion and git services commented on SOLR-16958:
--------------------------------------------------------

Commit 8c0d1a0698ca8a9d8d95d0e1de5ccc8a4ec7dc56 in solr's branch 
refs/heads/main from Colvin Cowie
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=8c0d1a0698c ]

SOLR-16958: Fix spurious warning about LATEST luceneMatchVersion (#1879)



> Spurious warning logged when using latest luceneMatchVersion
> ------------------------------------------------------------
>
>                 Key: SOLR-16958
>                 URL: https://issues.apache.org/jira/browse/SOLR-16958
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 9.2, 9.3, 9.2.1
>            Reporter: Colvin Cowie
>            Assignee: Colvin Cowie
>            Priority: Trivial
>
> Moving to Solr 9.3 I specified 
> {{<luceneMatchVersion>9.7.0</luceneMatchVersion>}} 
> In the logs I saw
> |SolrConfig|You should not use LATEST as luceneMatchVersion property: if you 
> use this setting,&#8203; and then Solr upgrades to a newer release of 
> Lucene,&#8203; sizable changes may happen. If precise back compatibility is 
> important then you should instead explicitly specify an actual Lucene 
> version.|
>  
> That's a result of 
> [https://github.com/apache/solr/commit/05f61f60bb631662035439f84edf5df9e06b5790#r126093986]
>  changing the comparison to use equals() rather than == as it did previously.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to