[
https://issues.apache.org/jira/browse/SOLR-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715967#comment-17715967
]
Jan Høydahl edited comment on SOLR-16769 at 4/24/23 8:05 PM:
-------------------------------------------------------------
{quote}there's no stable way to check whether a cluster level plugin has been
added or not.
{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?
was (Author: janhoy):
{quote}there's no stable way to check whether a cluster level plugin has been
added or not.
{quote}
Instead of documenting internal APIs, I think the correct action here is start
adding such APIs. What about the
[https://solr.apache.org/guide/solr/latest/configuration-guide/cluster-plugins.html#list-plugins]
API, is it not enough?
> /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: 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
