I was testing the RC manually , and then when I went to create the ".system" collection I noticed this in the logs:
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. Anyone more familiar with the ".system" collection and which config set it picks ? The default config set has luceneMatchVersion = 7.4.0 . And how important is this issue? On Tue, Jun 19, 2018 at 1:07 PM, Alan Woodward <[email protected]> wrote: > +1 > > SUCCESS! [1:57:22.136590] > > > On 18 Jun 2018, at 21:27, Adrien Grand <[email protected]> wrote: > > Please vote for release candidate 1 for Lucene/Solr 7.4.0 > > The artifacts can be downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.4.0-RC1- > rev9060ac689c270b02143f375de0348b7f626adebc > > You can run the smoke tester directly with this command: > > python3 -u dev-tools/scripts/smokeTestRelease.py \ > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.4.0-RC1- > rev9060ac689c270b02143f375de0348b7f626adebc > > > <https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.3.0-RC1-reveb8a5a882f879a51389b5d43f74f3aceac9e68c9> > Here’s my +1 > SUCCESS! [0:48:15.228535] > > >
