[
https://issues.apache.org/jira/browse/SOLR-14303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690447#comment-17690447
]
Jan Høydahl commented on SOLR-14303:
------------------------------------
Let's find out what is lacking to port UI over to {{{}/api/cluster/zk{}}}. It's
used by both Cloud->Tree and Cloud->Graph views.
The old {{/admin/zookeeper}} api returns a full nested tree structure in one
single call, while the {{/api/cluster/zk}} only returns the nodes on one level
along with number of children:
!Skjermbilde 2023-02-17 kl. 15.49.59.png!!Skjermbilde 2023-02-17 kl.
15.51.07.png!
Zookeeper is abstracted as a "Service" in Angular:
!Skjermbilde 2023-02-17 kl. 16.18.43.png!
Each of these return the plain data from admin/zookeeper as string, but the
consumers (tree and graph) rely on that string being of that specific format,
with metadata and text content in various json attributes. So the bigger job
will be rewriting all those places. Perhaps even the presentation layer (html)
assumes something about the structure?
Also, the lack of a "recursive" list of znodes in the new API means we need
potentially hundreds/thousands of requests to build the full tree for a large
cluster. So perhaps the new API also needs some extention?
> Deprecate /admin/zookeeper
> --------------------------
>
> Key: SOLR-14303
> URL: https://issues.apache.org/jira/browse/SOLR-14303
> Project: Solr
> Issue Type: Bug
> Reporter: Ishan Chattopadhyaya
> Priority: Major
> Attachments: Skjermbilde 2023-02-17 kl. 15.49.59.png, Skjermbilde
> 2023-02-17 kl. 15.51.07.png, Skjermbilde 2023-02-17 kl. 16.18.43.png
>
>
> This is a spinoff from SOLR-13942 to deprecate /admin/zookeeper and cutover
> the admin UI to the new API proposed there (/cluster/zk).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
