[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051016#comment-17051016
]
Jan Høydahl commented on SOLR-13942:
------------------------------------
Linked up [GitHub Pull Request
#1309|https://github.com/apache/lucene-solr/pull/1309] which was created March
3rd 2010 11:19 UTC with an empty PR description, commit hash
4498b9c360609abd813f57532189be16a6b9d823 and commit message "initial commit
with test" and then immediately merged to master. The lack of jira-reference in
commit message is probably the reason why gitbot did not catch it for comment.
I'm concerned for tech reasons but more so for community reasons. We have CTR
but not commit-then-forgive. Code must both be high quality an undisputed for
CTR to work.
> /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: Major
> 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
