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

Shalin Shekhar Mangar edited comment on SOLR-5756 at 8/7/15 6:24 PM:
---------------------------------------------------------------------

# I changed the Collection API from using "name" to "collection" which, to me, 
seems much more clear.
# I added a end-to-end test in TestCollectionAPI to migrate state format using 
the new collection API.
# Added SolrJ support (CollectionAdminRequest.MigrateStateFormat)


was (Author: shalinmangar):
# I changed the Collection API from using "name" to "collection" which, to me, 
seems much more clear.
# I added a end-to-end test in TestCollectionAPI to migrate state format using 
the new collection API.

> A utility API to move collections from stateFormat=1 to stateFormat=2
> ---------------------------------------------------------------------
>
>                 Key: SOLR-5756
>                 URL: https://issues.apache.org/jira/browse/SOLR-5756
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Noble Paul
>            Assignee: Shalin Shekhar Mangar
>             Fix For: Trunk, 5.4
>
>         Attachments: SOLR-5756-part2.patch, SOLR-5756-trunk.patch, 
> SOLR-5756.patch, SOLR-5756.patch, SOLR-5756.patch
>
>
> SOLR-5473 allows creation of collection with state stored outside of 
> clusterstate.json. We would need an API to  move existing 'internal' 
> collections outside



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to