[
https://issues.apache.org/jira/browse/SOLR-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14910205#comment-14910205
]
Upayavira commented on SOLR-8083:
---------------------------------
I'm in support of that separation.
How would you expect the admin UI to implement the tree browser without using
the /admin/zookeeper API?
I do see a number of situations where functionality has been placed one side or
the other based upon what people know how to do, rather than on where it should
be. It'd be great to fix those.
Regarding /zookeeper, that is sufficiently fundamental a feature that we must
make such a change work across both the old and new UIs. Using your new API
(#2) could be done in the new UI only.
> Convert the ZookeeperInfoServlet to a handler at /admin/zookeeper
> ------------------------------------------------------------------
>
> Key: SOLR-8083
> URL: https://issues.apache.org/jira/browse/SOLR-8083
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Assignee: Noble Paul
> Attachments: SOLR-8083.patch
>
>
> There is no need to have an extra servlet for this purpose
> By keeping this outside of Solr we cannot even secure it properly using the
> security framework and now we have taken up a top level name called zookeeper
> which cannot be used as a collection name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
