[
https://issues.apache.org/jira/browse/SOLR-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072558#comment-13072558
]
Hoss Man commented on SOLR-2667:
--------------------------------
Stefan: looking at the example on trunk today i realized one oddity i've never
noticed before. The left nav lists "singlecore" as the lable for getting
collection specific information, even though the example configs do infact have
a solr.xml containing info about the one core, and it's name is "collection1"
I understand that you have special logic for the "single core" case because of
legacy installs that might not have any solr.xml, so there can never be more
then one core because no adminPath is defined -- but in the case the core does
in fact have a name, and new cores can be added with new names (i tested, it
works and new cores show up in the admin bueatifully) -- so i don't understand
why "collection1" show up as "singlecore" (even after adding additional cores)
> Finish Solr Admin UI
> --------------------
>
> Key: SOLR-2667
> URL: https://issues.apache.org/jira/browse/SOLR-2667
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Fix For: 4.0
>
> Attachments: SOLR-2667-110722.patch
>
>
> In SOLR-2399, we added a new admin UI. The issue has gotten too long to
> follow, so this is a new issue to track remaining tasks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
