[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050627#comment-17050627
]
Tomas Eduardo Fernandez Lobbe edited comment on SOLR-13942 at 3/3/20 11:16 PM:
-------------------------------------------------------------------------------
bq. whether we use ZK or something else to store our shared data
But you see that the name of the endpoint is "zk", right? or am I missing
something?
bq. You understand the difference between exposing zookeeper and exposing data
in zookeeper, right?
The "data" inside ZooKeeper is cluster metadata, that's subject to change
without compatibility or any warnings. By providing an API, that people start
building on top of, you need to start supporting compatibility.
bq. This is a diagnostic tool.
Can we start here? what's the information that you are looking to find that
belongs to a Solr API and it's not part of one today?
bq. 3.5 months is not "hurry". This issue has been under discussion since
November.
The PR was created and merged in exactly 15 minutes.
https://github.com/apache/lucene-solr/pull/1309. With absolutely no review.
Even if the discussion in this Jira issue was not settled. [~ichattopadhyaya],
I won't believe you if you tell me you looked at the code, it has a {{main}}
and the test is a joke.
bq. Mostly, the fears were unfounded and unsubstantiated
well, that's your opinion. I do think you should revert until consensus is
achieved.
was (Author: tomasflobbe):
bq. whether we use ZK or something else to store our shared data
But you see that the name of the endpoint is "zk", right? or am I missing
something?
bq. You understand the difference between exposing zookeeper and exposing data
in zookeeper, right?
The "data" inside ZooKeeper is cluster metadata, that's subject to change
without compatibility or any warnings. By providing an API, that people start
building on top of, you need to start supporting compatibility.
bq. This is a diagnostic tool.
Can we start here? what's the information that you are looking to find that
belongs to a Solr API and it's not part of one today?
bq. 3.5 months is not "hurry". This issue has been under discussion since
November.
The PR was created and merged in exactly 15 minutes.
https://github.com/apache/lucene-solr/pull/1309. With absolutely no review.
Even if the discussion in this Jira issue was not settled. [~ichattopadhyaya],
I won't believe you if you tell me you looked at the code, it has a `main` and
the test is a joke.
bq. Mostly, the fears were unfounded and unsubstantiated
well, that's your opinion. I do think you should revert until consensus is
achieved.
> /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: 10m
> 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
