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

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
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
            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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org

     [ 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Mark Miller updated SOLR-2127:
------------------------------

    Attachment: SOLR-2127.patch

Probably more to come here - but this patch adds writing out the defaultCoreName to the persist method, and adds a test for this.

> 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
>         Attachments: 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922951#action_12922951 ]

Mark Miller commented on SOLR-2127:
-----------------------------------

I'm still looking to see if there are more problems here, but I have committed the issue covered in the current patch - that is/was a clear and simple to address bug. I just want to make sure there is not another part to this before resolving.

> 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
>
>
> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Mark Miller updated SOLR-2127:
------------------------------

    Fix Version/s: 4.0
                   3.1

> 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
>
>
> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Ephraim Ofir updated SOLR-2127:
-------------------------------

    Attachment: SOLR-2127.patch

Fixed indentation of solr.xml when serializing and added to CHANGES.txt

> 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: [hidden email]
For additional commands, e-mail: [hidden email]