[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051247#comment-17051247
]
Ishan Chattopadhyaya commented on SOLR-13942:
---------------------------------------------
bq. because you've just added a new, powerful and totally undocumented API to
Solr just a moment before the release, and when he pushed back you largely
ignored his concerns instead of trying to find a better solution.
This isn't any more powerful than an already existing API; just cleaner. All of
his concerns were addressed. Please let me know if we've overlooked or missed
any of his specific concerns that we haven't addressed yet.
bq. So, in CTR workflow, if there are valid concerns and the original committer
ignores them, IMHO a veto is a justified way to draw his attention and force
the discussion, in order to arrive at a better solution.
I still don't see a technical reason for the veto, but a few questions (which
Jason asked in the past and summarized again and answered).
https://www.apache.org/foundation/voting.html#Veto
{quote}
Here's my strawman proposal how to proceed:
revert (or don't revert) but address Jan's concerns before the 8.5 release,
plus:
mark the API as experimental, both in the docs and in the API output
add RefGuide documentation
add more tests - this is a powerful new API and it has just one basic test?
come on.
{quote}
I agree with doing all this, but this can be done without the veto/revert. Btw,
I don't see how this is a "powerful new API", and a unit test to validate
whether ZK's data is actually being returned is insufficient.
> /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
