[ 
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051587#comment-17051587
 ] 

Ishan Chattopadhyaya commented on SOLR-13942:
---------------------------------------------

bq. I'm happy to continue discussing them, 
Glad.

bq. but in the meantime, given that they are technical reasons, you need to 
revert the commit
Noble's commits, he should consider when he's back up online :-)

bq. I don't understand why this needs to be in 8.x right before a release
It really doesn't *need to*. Jan marked this as a release blocker, so he might 
have some reason? From my perspective, I see that this work was finished before 
branch was cut, so it can go into 8.5.

bq. If this is an API that's going to change then can we put it in 9.0 and let 
it brew a little bit before maturing? 
This API isn't going to change in forseeable future. If we replace ZK with 
etcd, then maybe so.


> /api/cluster/zk/* to fetch raw ZK data
> --------------------------------------
>
>                 Key: SOLR-13942
>                 URL: https://issues.apache.org/jira/browse/SOLR-13942
>             Project: Solr
>          Issue Type: New Feature
>          Components: v2 API
>            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

Reply via email to