message in context:
http://lucene.472066.n3.nabble.com/rename-a-core-to-same-name-of-existing-core-tp3090960p4063047.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 5/13/2013 11:46 AM, Jie Sun wrote:
did any one verified the following is ture?
the Description on http://wiki.apache.org/solr/CoreAdmin#CREATE is:
*quote*
If a core with the same name exists, while the "new" created core is
initalizing, the "old" one will continue to accept requests. Once it
(30 documents):
http://myhost.com:8080/solr/abc/select/?q=type%3Amessage&version=2.2&start=0&rows=10&indent=on
10
I thought the old core should be unloaded?
did I misunderstand any thing here?
thanks
Jie
--
View this message in context:
http://lucene.472066.n3.nabble.com/rename-a-core-to-same-name-of-existing-core-tp3090960p4063008.html
Sent from the Solr - User mailing list archive at Nabble.com.
Stefan,
> I guess, same handling for other actions, like rename.
I agree. Thank you for the pointer!
koji
(11/06/22 23:16), Stefan Matheis wrote:
Koji,
the Description on http://wiki.apache.org/solr/CoreAdmin#CREATE is:
*quote*
If a core with the same name exists, while the "new" created co
Koji,
the Description on http://wiki.apache.org/solr/CoreAdmin#CREATE is:
*quote*
If a core with the same name exists, while the "new" created core is
initalizing, the "old" one will continue to accept requests. Once it
has finished, all new request will go to the "new" core, and the "old"
core w
I accidentally rename a core to the same name of existing core, e.g. using
example-DIH:
http://localhost:8983/solr/admin/cores?action=RENAME&core=db&other=tika
I expected solr throws an exception, but it worked, and the existing core
(tika) is gone.
Does it a known bug (but I couldn't find open
