You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by André Widhani <An...@digicol.de> on 2013/05/23 16:45:36 UTC
Core admin action "CREATE" fails for existing core
It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
Is this change intended?
André
AW: Core admin action "CREATE" fails for existing core
Posted by André Widhani <An...@digicol.de>.
Added the issue.
https://issues.apache.org/jira/browse/SOLR-4857
"Core admin action RELOAD lacks requests parameters to point core to another config or schema file or data dir"
________________________________________
Von: André Widhani [Andre.Widhani@digicol.de]
Gesendet: Donnerstag, 23. Mai 2013 23:13
An: solr-user@lucene.apache.org
Betreff: AW: Core admin action "CREATE" fails for existing core
Ok - yes, will do so tomorrow.
Thanks,
André
________________________________________
Von: Mark Miller [markrmiller@gmail.com]
Gesendet: Donnerstag, 23. Mai 2013 22:46
An: solr-user@lucene.apache.org
Betreff: Re: Core admin action "CREATE" fails for existing core
Your right - that does seem to be a new limitation. Could you create a JIRA issue for it?
It would be fairly simple to add another reload method that also took the name of a new solrconfig/schema file.
- Mark
On May 23, 2013, at 4:11 PM, André Widhani <An...@digicol.de> wrote:
> Mark, Alan,
>
> thanks for explaining and updating the wiki.
>
> When reloading the core using action=CREATE with Solr 4.1 I could specify the path to schema and config. In fact I used this to reconfigure the core to use a specific one of two prepared config files depending on some external index state (instead of making changes to one and the same config file).
>
> action=RELOAD does not understand the corresponding request parameters "schema" and "config" (which is why I used CREATE, not RELOAD in the first place). So the functionality to switch to a different config file for an existing core is no longer there, I guess?
>
> Thanks,
> André
>
> ________________________________________
> Von: Alan Woodward [alan@flax.co.uk]
> Gesendet: Donnerstag, 23. Mai 2013 18:43
> An: solr-user@lucene.apache.org
> Betreff: Re: Core admin action "CREATE" fails for existing core
>
> Thanks!
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 23 May 2013, at 17:38, Steve Rowe wrote:
>
>> Alan, I've added AlanWoodward to the Solr AdminGroup page.
>>
>> On May 23, 2013, at 12:29 PM, Alan Woodward <al...@flax.co.uk> wrote:
>>
>>> I think the wiki needs to be updated to reflect this? http://wiki.apache.org/solr/CoreAdmin
>>>
>>> If somebody adds me as an editor (AlanWoodward), I'll do it.
>>>
>>> Alan Woodward
>>> www.flax.co.uk
>>>
>>>
>>> On 23 May 2013, at 16:43, Mark Miller wrote:
>>>
>>>> Yes, this did change - it's actually a protection for a previous change though.
>>>>
>>>> There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
>>>>
>>>> Sorry about the inconvenience.
>>>>
>>>> - Mark
>>>>
>>>> On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
>>>>
>>>>> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>>>>>
>>>>> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>>>>>
>>>>> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>>>>>
>>>>> Is this change intended?
>>>>>
>>>>> André
>>>>>
>>>>
>>>
>>
>
AW: Core admin action "CREATE" fails for existing core
Posted by André Widhani <An...@digicol.de>.
Ok - yes, will do so tomorrow.
Thanks,
André
________________________________________
Von: Mark Miller [markrmiller@gmail.com]
Gesendet: Donnerstag, 23. Mai 2013 22:46
An: solr-user@lucene.apache.org
Betreff: Re: Core admin action "CREATE" fails for existing core
Your right - that does seem to be a new limitation. Could you create a JIRA issue for it?
It would be fairly simple to add another reload method that also took the name of a new solrconfig/schema file.
- Mark
On May 23, 2013, at 4:11 PM, André Widhani <An...@digicol.de> wrote:
> Mark, Alan,
>
> thanks for explaining and updating the wiki.
>
> When reloading the core using action=CREATE with Solr 4.1 I could specify the path to schema and config. In fact I used this to reconfigure the core to use a specific one of two prepared config files depending on some external index state (instead of making changes to one and the same config file).
>
> action=RELOAD does not understand the corresponding request parameters "schema" and "config" (which is why I used CREATE, not RELOAD in the first place). So the functionality to switch to a different config file for an existing core is no longer there, I guess?
>
> Thanks,
> André
>
> ________________________________________
> Von: Alan Woodward [alan@flax.co.uk]
> Gesendet: Donnerstag, 23. Mai 2013 18:43
> An: solr-user@lucene.apache.org
> Betreff: Re: Core admin action "CREATE" fails for existing core
>
> Thanks!
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 23 May 2013, at 17:38, Steve Rowe wrote:
>
>> Alan, I've added AlanWoodward to the Solr AdminGroup page.
>>
>> On May 23, 2013, at 12:29 PM, Alan Woodward <al...@flax.co.uk> wrote:
>>
>>> I think the wiki needs to be updated to reflect this? http://wiki.apache.org/solr/CoreAdmin
>>>
>>> If somebody adds me as an editor (AlanWoodward), I'll do it.
>>>
>>> Alan Woodward
>>> www.flax.co.uk
>>>
>>>
>>> On 23 May 2013, at 16:43, Mark Miller wrote:
>>>
>>>> Yes, this did change - it's actually a protection for a previous change though.
>>>>
>>>> There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
>>>>
>>>> Sorry about the inconvenience.
>>>>
>>>> - Mark
>>>>
>>>> On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
>>>>
>>>>> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>>>>>
>>>>> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>>>>>
>>>>> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>>>>>
>>>>> Is this change intended?
>>>>>
>>>>> André
>>>>>
>>>>
>>>
>>
>
Re: Core admin action "CREATE" fails for existing core
Posted by Mark Miller <ma...@gmail.com>.
Your right - that does seem to be a new limitation. Could you create a JIRA issue for it?
It would be fairly simple to add another reload method that also took the name of a new solrconfig/schema file.
- Mark
On May 23, 2013, at 4:11 PM, André Widhani <An...@digicol.de> wrote:
> Mark, Alan,
>
> thanks for explaining and updating the wiki.
>
> When reloading the core using action=CREATE with Solr 4.1 I could specify the path to schema and config. In fact I used this to reconfigure the core to use a specific one of two prepared config files depending on some external index state (instead of making changes to one and the same config file).
>
> action=RELOAD does not understand the corresponding request parameters "schema" and "config" (which is why I used CREATE, not RELOAD in the first place). So the functionality to switch to a different config file for an existing core is no longer there, I guess?
>
> Thanks,
> André
>
> ________________________________________
> Von: Alan Woodward [alan@flax.co.uk]
> Gesendet: Donnerstag, 23. Mai 2013 18:43
> An: solr-user@lucene.apache.org
> Betreff: Re: Core admin action "CREATE" fails for existing core
>
> Thanks!
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 23 May 2013, at 17:38, Steve Rowe wrote:
>
>> Alan, I've added AlanWoodward to the Solr AdminGroup page.
>>
>> On May 23, 2013, at 12:29 PM, Alan Woodward <al...@flax.co.uk> wrote:
>>
>>> I think the wiki needs to be updated to reflect this? http://wiki.apache.org/solr/CoreAdmin
>>>
>>> If somebody adds me as an editor (AlanWoodward), I'll do it.
>>>
>>> Alan Woodward
>>> www.flax.co.uk
>>>
>>>
>>> On 23 May 2013, at 16:43, Mark Miller wrote:
>>>
>>>> Yes, this did change - it's actually a protection for a previous change though.
>>>>
>>>> There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
>>>>
>>>> Sorry about the inconvenience.
>>>>
>>>> - Mark
>>>>
>>>> On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
>>>>
>>>>> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>>>>>
>>>>> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>>>>>
>>>>> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>>>>>
>>>>> Is this change intended?
>>>>>
>>>>> André
>>>>>
>>>>
>>>
>>
>
AW: Core admin action "CREATE" fails for existing core
Posted by André Widhani <An...@digicol.de>.
Mark, Alan,
thanks for explaining and updating the wiki.
When reloading the core using action=CREATE with Solr 4.1 I could specify the path to schema and config. In fact I used this to reconfigure the core to use a specific one of two prepared config files depending on some external index state (instead of making changes to one and the same config file).
action=RELOAD does not understand the corresponding request parameters "schema" and "config" (which is why I used CREATE, not RELOAD in the first place). So the functionality to switch to a different config file for an existing core is no longer there, I guess?
Thanks,
André
________________________________________
Von: Alan Woodward [alan@flax.co.uk]
Gesendet: Donnerstag, 23. Mai 2013 18:43
An: solr-user@lucene.apache.org
Betreff: Re: Core admin action "CREATE" fails for existing core
Thanks!
Alan Woodward
www.flax.co.uk
On 23 May 2013, at 17:38, Steve Rowe wrote:
> Alan, I've added AlanWoodward to the Solr AdminGroup page.
>
> On May 23, 2013, at 12:29 PM, Alan Woodward <al...@flax.co.uk> wrote:
>
>> I think the wiki needs to be updated to reflect this? http://wiki.apache.org/solr/CoreAdmin
>>
>> If somebody adds me as an editor (AlanWoodward), I'll do it.
>>
>> Alan Woodward
>> www.flax.co.uk
>>
>>
>> On 23 May 2013, at 16:43, Mark Miller wrote:
>>
>>> Yes, this did change - it's actually a protection for a previous change though.
>>>
>>> There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
>>>
>>> Sorry about the inconvenience.
>>>
>>> - Mark
>>>
>>> On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
>>>
>>>> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>>>>
>>>> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>>>>
>>>> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>>>>
>>>> Is this change intended?
>>>>
>>>> André
>>>>
>>>
>>
>
Re: Core admin action "CREATE" fails for existing core
Posted by Alan Woodward <al...@flax.co.uk>.
Thanks!
Alan Woodward
www.flax.co.uk
On 23 May 2013, at 17:38, Steve Rowe wrote:
> Alan, I've added AlanWoodward to the Solr AdminGroup page.
>
> On May 23, 2013, at 12:29 PM, Alan Woodward <al...@flax.co.uk> wrote:
>
>> I think the wiki needs to be updated to reflect this? http://wiki.apache.org/solr/CoreAdmin
>>
>> If somebody adds me as an editor (AlanWoodward), I'll do it.
>>
>> Alan Woodward
>> www.flax.co.uk
>>
>>
>> On 23 May 2013, at 16:43, Mark Miller wrote:
>>
>>> Yes, this did change - it's actually a protection for a previous change though.
>>>
>>> There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
>>>
>>> Sorry about the inconvenience.
>>>
>>> - Mark
>>>
>>> On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
>>>
>>>> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>>>>
>>>> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>>>>
>>>> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>>>>
>>>> Is this change intended?
>>>>
>>>> André
>>>>
>>>
>>
>
Re: Core admin action "CREATE" fails for existing core
Posted by Steve Rowe <sa...@gmail.com>.
Alan, I've added AlanWoodward to the Solr AdminGroup page.
On May 23, 2013, at 12:29 PM, Alan Woodward <al...@flax.co.uk> wrote:
> I think the wiki needs to be updated to reflect this? http://wiki.apache.org/solr/CoreAdmin
>
> If somebody adds me as an editor (AlanWoodward), I'll do it.
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 23 May 2013, at 16:43, Mark Miller wrote:
>
>> Yes, this did change - it's actually a protection for a previous change though.
>>
>> There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
>>
>> Sorry about the inconvenience.
>>
>> - Mark
>>
>> On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
>>
>>> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>>>
>>> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>>>
>>> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>>>
>>> Is this change intended?
>>>
>>> André
>>>
>>
>
Re: Core admin action "CREATE" fails for existing core
Posted by Alan Woodward <al...@flax.co.uk>.
I think the wiki needs to be updated to reflect this? http://wiki.apache.org/solr/CoreAdmin
If somebody adds me as an editor (AlanWoodward), I'll do it.
Alan Woodward
www.flax.co.uk
On 23 May 2013, at 16:43, Mark Miller wrote:
> Yes, this did change - it's actually a protection for a previous change though.
>
> There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
>
> Sorry about the inconvenience.
>
> - Mark
>
> On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
>
>> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>>
>> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>>
>> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>>
>> Is this change intended?
>>
>> André
>>
>
Re: Core admin action "CREATE" fails for existing core
Posted by Mark Miller <ma...@gmail.com>.
Yes, this did change - it's actually a protection for a previous change though.
There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code.
Sorry about the inconvenience.
- Mark
On May 23, 2013, at 10:45 AM, André Widhani <An...@digicol.de> wrote:
> It seems to me that the behavior of the Core admin action "CREATE" has changed when going from Solr 4.1 to 4.3.
>
> With 4.1, I could re-configure an existing core (changing path/name to solrconfig.xml for example). In 4.3, I get an error message:
>
> SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore 'core-tex69b6iom1djrbzmlmg83-index2': Core with name 'core-tex69b6iom1djrbzmlmg83-index2' already exists.
>
> Is this change intended?
>
> André
>