[
https://issues.apache.org/jira/browse/SOLR-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715814#comment-17715814
]
Ishan Chattopadhyaya commented on SOLR-16769:
---------------------------------------------
Btw, the new {{http://localhost:8983/api/cluster/zookeeper/}} API endpoint (or
even /data at the end) throws 404.
{code}
{
"responseHeader": {
"status": 404,
"QTime": 1
},
"error": {
"metadata": {
"error-class": "org.apache.solr.common.SolrException",
"root-error-class": "org.apache.solr.common.SolrException"
},
"msg": "Cannot find API for the path: /cluster/zookeeper",
"code": 404
}
}
{code}
Of course, {{/children}} works. This bug just makes it hard for a user to
discover the correct endpoint, without any help by way of upgrade notice.
> /api/cluster/zk endpoint removed in non-backward compatible manner
> ------------------------------------------------------------------
>
> Key: SOLR-16769
> URL: https://issues.apache.org/jira/browse/SOLR-16769
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 9.2
> Reporter: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: 9.3, 9.2.1
>
> Attachments: Skjermbilde 2023-04-24 kl. 15.09.38.png
>
>
> In https://issues.apache.org/jira/browse/SOLR-16488, backward compatability
> has been broken when the above mentioned endpoint was removed.
> I think right way should be to retain the older endpoint (deprecated), and
> introduce the new endpoints that are designed to replace it. In 10x, the
> older endpoint can be removed.
--
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
