[
https://issues.apache.org/jira/browse/SOLR-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14910160#comment-14910160
]
Noble Paul commented on SOLR-8083:
----------------------------------
Thanks,
I would like to make the whole thing split into two
# get rid of the servlet and make it just a normal request handler. This step
would just return the same output as it used to. So, really nothing changes
other than the path at which this is accessed
# Enhance the standard APIs in such a way that the admin UI can be completely
driven using them. The standard APIs will have proper JUnit tests and a well
known output. The current output is driven by the UI and not the other way
around.
I would say we open a ticket for #2 and track it separately and the admin ui
should eventually stop depending on the {{/admin/zookeeper}} end point.
> 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]
