[
https://issues.apache.org/jira/browse/SOLR-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715945#comment-17715945
]
Ishan Chattopadhyaya commented on SOLR-16769:
---------------------------------------------
{quote} If a 3rd-party project wants to rely on an API that we've signaled is
"in-flux" in so many ways, I sympathize with them. I absolutely do. But there's
not much we can do to soften the consequences for folks if they choose to
develop against Solr's bleeding edge.
{quote}
No one chooses to develop against Solr's bleeding edge, they are forced to. In
this particular case (Yasa), there's no stable way to check whether a cluster
level plugin has been added or not. Looking up the clusterprops in ZK is the
best way right now.
Changing an experimental API in a minor release is fine, but removing it
without any reasonable notice or even a proper upgrade notice is cruel. Esp.
for an API for which a supported alternative doesn't exist. Just shows how less
we care about users.
> /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
