You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2010/10/13 16:22:33 UTC

[jira] Assigned: (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 ""

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

Mark Miller reassigned SOLR-2127:
---------------------------------

    Assignee: Mark Miller

> 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
>
> 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