Update luceneMatchVersion in solrconfig.xml

[cjcolvar]

Description

The luceneMatchVersion in our solrconfig.xml still says 5.0.0 which produces deprecation warnings when starting up solr. We should evaluate what a good version should be and if it impacts any of our queries. Bumping the version will also require a full reindex (see https://solr.apache.org/guide/solr/latest/indexing-guide/reindexing.html#solrconfig-changes).

solr-1  | 2025-01-08 18:51:35.311 INFO  (coreLoadExecutor-13-thread-1) [c: s: r: x:avalon t:] o.a.s.c.SolrConfig Using Lucene MatchVersion: 5.0.0
solr-1  | 2025-01-08 18:51:35.382 WARN  (coreLoadExecutor-13-thread-1) [c: s: r: x:avalon t:] o.a.s.s.FieldTypePluginLoader TokenizerFactory is using deprecated 5.0.0 emulation. You should at some point declare and reindex to at least 8.0, because 7.x emulation is deprecated and will be removed in 9.0

There are other deprecation warnings that should be explored as well:

solr-1  | 2025-01-08 18:51:35.335 WARN  (coreLoadExecutor-13-thread-1) [c: s: r: x:avalon t:] o.a.s.c.SolrConfig Ignored deprecated enableRemoteStreaming in config; use sys-prop
solr-1  | 2025-01-08 18:51:35.416 WARN  (main) [c: s: r: x: t:] o.g.j.m.i.MessagingBinders A class jakarta.activation.DataSource for a default provider MessageBodyWriter<jakarta.activation.DataSource> was not found. The provider is not available.
solr-1  | 2025-01-08 18:51:35.473 WARN  (coreLoadExecutor-13-thread-1) [c: s: r: x:avalon t:] o.a.s.s.AbstractSpatialPrefixTreeFieldType FieldType DateRangeField does not allow omitNorms to be specified in schema, hardcoded behavior is omitNorms=true
solr-1  | 2025-01-08 18:51:35.473 WARN  (coreLoadExecutor-13-thread-1) [c: s: r: x:avalon t:] o.a.s.s.AbstractSpatialPrefixTreeFieldType FieldType DateRangeField does not allow omitTermFreqAndPositions to be specified in schema, hardcoded behavior is omitTermFreqAndPositions=true

Done Looks Like

• Bump luceneMatchVersion
• Explore deprecation warnings and resolve

[joncameron]

We'll be forced to do this when upgrading to 10. If this does go away in a later Solr 9.x version, we'll catch it with CircleCI against the Solr 9 Docker image.