[
https://issues.apache.org/jira/browse/SOLR-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691230#comment-13691230
]
Mark Miller commented on SOLR-4943:
-----------------------------------
bq. Sorry, I didn't mean remove the URLs with the cores on them, I meant the
constructor functions.
Yes, I know, but the two are very related ;)
bq. So for example InfoHandler has a no-argument constructor, that sets this.cc
to null.
Right, like I said, that's a copy paste from the CoreAdmin class - it can
likely go.
bq. because they could be defined in solrconfig.xml as request handlers, and
need to go through the normal construct/init/inform lifecycle.
Exactly. This issue is not about removing the per core admin info - it's just
about adding that info at the system level so that the UI can be reasonable
when no SolrCores are defined.
> Add a new info admin handler.
> -----------------------------
>
> Key: SOLR-4943
> URL: https://issues.apache.org/jira/browse/SOLR-4943
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 5.0, 4.4
>
> Attachments: SOLR-4943-2.patch, SOLR-4943-3.patch, SOLR-4943.patch
>
>
> Currently, you have to specify a core to get system information for a variety
> of request handlers - properties, logging, thread dump, system, etc.
> These should be available at a system location and not core specific location.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
