[SOLR-17304] PKG_VERSIONS not honored when loading the schema plugins

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 9.6
• Fix Version/s: 9.7
• Component/s: Package Manager
• Assignee: Eric Pugh
• Reporter: Andrey Bozhko
• Created: 21/May/24 16:05
• Updated: 06/Jun/24 12:58
• Resolved: 06/Jun/24 12:58

Description

If the schema references plugin classes from the package uploaded to the package store, Solr always uses the latest version of the package when loading the schema even if the constraint is specified in params.json.

Steps to reproduce

1. Upload multiple versions of the same package to Solr (the versions don't have to be compatible with each other)
2. Upload a configset which requests a specific package version via PKG_VERSIONS in params.json
3. Create a collection using the uploaded configset

Expected behavior

• If the configsets references custom classes from the package, then Solr uses the package version constraint from params.json to initialize all the plugins mentioned in `solrconfig.xml` and `schema.xml`

Actual behavior

• Solr uses the package version specified in params.json only for loading the `solrconfig.xml` plugins
• For `schema.xml` plugins (field types, token filters, similarities, etc.) Solr always goes for the latest available package version, regardless of what was specified in params.json

Test that reproduces the issue: https://github.com/apache/solr/pull/2471.

Issue Links

• links to: GitHub Pull Request #2471