Back in the day I also wrote a blog post about this param: https://sease.io/2021/04/lucenematchversion-in-apache-solr.html
Hope it helps! Cheers -------------------------- *Alessandro Benedetti* Director @ Sease Ltd. *Apache Lucene/Solr Committer* *Apache Solr PMC Member* e-mail: a.benede...@sease.io *Sease* - Information Retrieval Applied Consulting | Training | Open Source Website: Sease.io <http://sease.io/> LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter <https://twitter.com/seaseltd> | Youtube <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github <https://github.com/seaseltd> On Thu, 31 Aug 2023 at 06:51, Shawn Heisey <apa...@elyograg.org> wrote: > On 8/30/23 13:25, Oakley, Craig (NIH/NLM/NCBI) [C] wrote: > > In previous upgrades, we have set luceneMatchVersion to match our > version of Solr > > > > But we were noticing that Solr 9.2.1 uses Lucene version 9.4.2 > > > > Should we continue using the Solr version (as we have in the past) or > should luceneMatchVersion be 9.4.2 (as the name would imply)? > > The other reply you got is correct. That will affect Lucene. Since the > project split, Lucene is putting out new minor versions faster than Solr > is. > > The Solr version on my personal server is 9.4.0-SNAPSHOT, which has > Lucene 9.7.0. I currently have my lMV set to 10.10.10, which for all > currently released versions is effectively the same as LATEST ... except > that with LATEST, you get a warning in the solr log every time a core > starts up. > > The only time I would ever suggest using a setting that's not the same > as the Lucene version (or newer) is when you know for SURE that setting > an older version will enable older behavior that you need. This > happened to me with Solr 4.8.0, where a major bug in WordDelimiterFilter > was fixed, which broke some queries on that install. For a while, I had > lMV set to 4.7.0 on my dev install, until I was able to devise a new > schema that worked with the new behavior. > > Thanks, > Shawn > >
