[
https://issues.apache.org/jira/browse/SOLR-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715813#comment-17715813
]
Jan Høydahl commented on SOLR-16769:
------------------------------------
{quote}[~janhoy] , can you recommend a way whereby users can monitor the ZK
contents, which we won't be breaking within a major release, that too without a
notice?
{quote}
IMO ZK is and should be an implementation detail. Users who choose to rely on
internal ZK structure or internal APIs must bear the burden of testing and
upgrading their applications for new Solr versions. We could of course add an
upgrade note to the ref guide regarding the changed v2 api endpoints.
> /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
