[
https://issues.apache.org/jira/browse/SOLR-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716389#comment-17716389
]
Houston Putman commented on SOLR-16769:
---------------------------------------
{quote}Instead of documenting internal APIs, I think the correct action here is
start adding the missing public APIs. What about the
[https://solr.apache.org/guide/solr/latest/configuration-guide/cluster-plugins.html#list-plugins]
API, is it not enough?
{quote}
Completely agreed here.
I also agree that the endpoints were documented that they could change at
anytime, the community agreed on the "experimental" tag for this reason.
It's perfectly fine for y'all to add the old endpoint back in for the next
version (without removing the new one), but I don't think anything wrong has
occurred here.
> /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
>
> Attachments: Screen Shot 2023-04-25 at 8.15.52 AM.png, 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
