[jira] Resolved: (SOLR-2127) When using the defaultCoreName attribute, after performing a swap, solr.xml no longer contains the defaultCoreName attribute, and the core which was dafult is now renamed to ""

["Mark Miller (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller resolved SOLR-2127.
-------------------------------

    Resolution: Fixed

Ah - I had added a little test. Needed to merge the commit from a few months ago back to 3.x as well.

done in r1062566.

> When using the defaultCoreName attribute, after performing a swap, solr.xml no longer contains the defaultCoreName attribute, and the core which was dafult is now renamed to ""
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-2127
>                 URL: https://issues.apache.org/jira/browse/SOLR-2127
>             Project: Solr
>          Issue Type: Bug
>          Components: multicore
>    Affects Versions: 1.4.2, 1.5
>            Reporter: Ephraim Ofir
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 3.1, 4.0
>
>         Attachments: SOLR-2127.patch, SOLR-2127.patch
>
>
> Tried using the defaultCoreName attribute on a 2 core setup. After performing a swap, my solr.xml no longer contains the defaultCoreName attribute, and the core which was dafult is now renamed to "", so after restart of the process can't access it by it's former name and can't perform other operations on it such as rename, reload or swap... 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org