[
https://issues.apache.org/jira/browse/SOLR-16477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623996#comment-17623996
]
Alex Deparvu commented on SOLR-16477:
-------------------------------------
I was able to repro this bug via SolrJ client too
{code:java}
SolrClient client = getSolrClient();
SolrRequest request = new CollectionAdminRequest.Rename("films", "morefilms");
NamedList<Object> response = client.request(request);
System.out.println(response); {code}
response
{noformat}
{responseHeader={status=0, QTime=128}} {noformat}
behavior is the same, you are getting an alias called 'films' pointing to a
broken collection names 'morefilms'
> Collection RENAME api creates broken alias
> ------------------------------------------
>
> Key: SOLR-16477
> URL: https://issues.apache.org/jira/browse/SOLR-16477
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 9.0, 8.11.2
> Reporter: Alex Deparvu
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Renaming a collection results in a broken alias (name as the source param)
> pointing to a non-existent collection (named as the target param).
> Steps to reproduce:
> * First create a new collection
> {noformat}
> bin/solr create -c films -s 2 -rf 2
> {noformat}
> * Second issue rename call
> {noformat}
> > curl -X POST
> > "http://127.0.0.1:8983/solr/admin/collections?action=RENAME&name=films&target=morefilms";
> { "responseHeader":{ "status":0, "QTime":125}}
> {noformat}
>
> This will create an alias called 'films' pointing to a collection named
> 'morefilms', when it should be the other way around.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
