[
https://issues.apache.org/jira/browse/SOLR-17304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Bozhko updated SOLR-17304:
---------------------------------
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].
was:
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].
> PKG_VERSIONS not honored when loading the schema plugins
> --------------------------------------------------------
>
> Key: SOLR-17304
> URL: https://issues.apache.org/jira/browse/SOLR-17304
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Package Manager
> Affects Versions: 9.6
> Reporter: Andrey Bozhko
> Priority: Minor
>
> 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].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
