[
https://issues.apache.org/jira/browse/SOLR-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715805#comment-17715805
]
Ishan Chattopadhyaya edited comment on SOLR-16769 at 4/24/23 1:23 PM:
----------------------------------------------------------------------
I don't understand your logic here. You're saying we'll remove one undocumented
API, and add another undocumented API, but not accomodate users who might need
to rely on these APIs?
[~janhoy] , can you recommend a way wherebe users can monitor the ZK contents,
which we won't be breaking within a major release, that too without a notice?
was (Author: ichattopadhyaya):
I don't understand your logic here. You're saying we'll remove one undocumented
API with another undocumented API, but not accomodate users who might need to
rely on these APIs?
[~janhoy] , can you recommend a way wherebe users can monitor the ZK contents,
which we won't be breaking within a major release, that too without a 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: [email protected]
For additional commands, e-mail: [email protected]
