[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051223#comment-17051223
]
Jan Høydahl commented on SOLR-13942:
------------------------------------
{quote}Please state your technical reason for the veto
{quote}
These are summarized nicely by [Jason's comment|#comment-17050254].
* Where is the decision that all data in zk strictly public? What about
security.json?
* We have been trying to abstract away zk. So this API must be
tagged/documented clearly as internal.
* The proposal adds redundant API surface. Has there been done any analysis of
whether it is possible to cut over Admin UI from /admin/zookeeper to
/api/cluster/zk? The ZookeeperInfoHandler seems to do quite a lot more logic
than just shuffling bits from ZK to the client.
It is easy to add but hard and time consuming to take the community
responsibility to cut over to the new and get rid of old APIs, thus we add to
our tech debt for every release.
> /api/cluster/zk/* to fetch raw ZK data
> --------------------------------------
>
> Key: SOLR-13942
> URL: https://issues.apache.org/jira/browse/SOLR-13942
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Blocker
> Fix For: 8.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> example
> download the {{state.json}} of
> {code}
> GET http://localhost:8983/api/cluster/zk/collections/gettingstarted/state.json
> {code}
> get a list of all children under {{/live_nodes}}
> {code}
> GET http://localhost:8983/api/cluster/zk/live_nodes
> {code}
> If the requested path is a node with children show the list of child nodes
> and their meta data
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
