[
https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451455#comment-13451455
]
Otis Gospodnetic commented on SOLR-2605:
----------------------------------------
[~hossman_luc...@fucit.org] we were able to reproduce this with Solr 3.6.1. It
this something you could backport, so the next 3.6.* release doesn't have this
issue?
> CoreAdminHandler, different Output while 'defaultCoreName' is specified
> -----------------------------------------------------------------------
>
> Key: SOLR-2605
> URL: https://issues.apache.org/jira/browse/SOLR-2605
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Reporter: Stefan Matheis (steffkes)
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 4.0-ALPHA
>
> Attachments: SOLR-2399-admin-cores-default.xml,
> SOLR-2399-admin-cores.xml, SOLR-2605.patch, SOLR-2605.patch
>
>
> The attached XML-Files show the little difference between a defined
> {{defaultCoreName}}-Attribute and a non existing one.
> Actually the new admin ui checks for an core with empty name to set single- /
> multicore-settings .. it's a quick change to count the number of defined
> cores instead.
> But, will it be possible, to get the core-name (again)? One of both
> attributes would be enough, if that makes a difference :)
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
