[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050656#comment-17050656
]
Noble Paul edited comment on SOLR-13942 at 3/4/20 12:38 AM:
------------------------------------------------------------
{quote}The PR was created and merged in exactly 15 minutes.
{quote}
The original branch has been there for 3.5 months. I had to create a new one
because , git merge was not succeeding for some strange reason.
{quote}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.
{quote}
Data in Zookeeper is public data. It is not supposed to be fixed. Everyone
knows this. Do people write tools by reading data from Zk today? I'm sure they
do. Are they aware it can change? Yes. Why do they do it? They have no other
choice
tell me one good reason why I should not remove the {{/admin/zookeeper}}
endpoint and we already have consensus. Every single point that you raised
against this is valid for the existing API as well.
{quote}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?
{quote}
Yes, let's start with the overseer queue. and the leader election queue.
{quote}But you see that the name of the endpoint is "zk", right? or am I
missing something?
{quote}
The name does not matter. You can just have a prefix of "/sharedclusterdata" as
the prefix and it will be just fine
was (Author: noble.paul):
{quote}The PR was created and merged in exactly 15 minutes.
{quote}
The original branch has been there for 3.5 months. I had to create a new one
because , git merge was not succeeding for some strange reason.
{quote}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.
{quote}
Data in Zookeeper is public data. It is not supposed to be fixed. Everyone
knows this. Do people write tools by reading data from Zk today? I'm sure they
do. Are they aware it can change? Yes. Why do they do it? They have no other
choice
{quote}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?
{quote}
Yes, let's start with the overseer queue. and the leader election queue.
{quote}But you see that the name of the endpoint is "zk", right? or am I
missing something?
{quote}
The name does not matter. You can just have a prefix of "/sharedclusterdata" as
the prefix and it will be just fine
> /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
