You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Alex Deparvu (Jira)" <ji...@apache.org> on 2022/10/19 21:33:00 UTC

[jira] [Commented] (SOLR-16477) Collection RENAME api creates broken alias

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

Alex Deparvu commented on SOLR-16477:
-------------------------------------

I am working on a PR for this

> 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
>
> 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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org