Colvin Cowie created SOLR-17617:
-----------------------------------
Summary: v2 CollectionProp and InstallCoreData APIs are broken
Key: SOLR-17617
URL: https://issues.apache.org/jira/browse/SOLR-17617
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 9.6.1, 9.7, 9.6, 9.4.1, 9.5, 9.4, 9.2.1, 9.3, 9.1.1, 9.2,
9.1, 9.0
Reporter: Colvin Cowie
The PUT method on the v2 collectionprop API doesn't work, because
{{org.apache.solr.handler.admin.api.CollectionProperty}} doesn't have an
@Inject annotation [on its
constructor|https://github.com/apache/solr/blob/main/solr/core/src/java/org/apache/solr/handler/admin/api/CollectionProperty.java#L41]
That leads to a 500 response and errors like this in the logs
{quote}Caused by: java.lang.NoSuchMethodException: Could not find a suitable
constructor in org.apache.solr.handler.admin.api.CollectionProperty class.
at
org.glassfish.jersey.inject.hk2.JerseyClassAnalyzer.getConstructor(JerseyClassAnalyzer.java:168)
~[?:?]
...
_The following warnings have been detected: WARNING: HK2 service reification
failed for [org.apache.solr.handler.admin.api.CollectionProperty] with an
exception:_
{quote}
I've taken a quick look through the other transport classes, and the same
problem exists for {{{}org.apache.solr.handler.admin.api.InstallCoreData{}}}.
The rest look okay, but ideally we need a smoke test for each v2 API to verify
that all services are wired in correctly. The functionality is already tested
via v1 APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
