[
https://issues.apache.org/jira/browse/SOLR-16479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685942#comment-17685942
]
Jason Gerlowski commented on SOLR-16479:
----------------------------------------
Good catch Josh, thanks for calling this out!
> Support for `repository` parameter in v2 api for restores
> ---------------------------------------------------------
>
> Key: SOLR-16479
> URL: https://issues.apache.org/jira/browse/SOLR-16479
> Project: Solr
> Issue Type: Improvement
> Components: Backup/Restore, v2 API
> Affects Versions: 8.11.2
> Reporter: Josh Souza
> Priority: Major
> Labels: Backup/Restore, V2
>
> The v1 API for restoring from backups
> ([https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#restore|https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#restore)]
> )
> includes the optional parameter `repository`, which can be utilized to
> trigger restores from a particular backup repository. However, the v2 api,
> located at `api/collections?command=restore-collection`, does not include
> this parameter.
> While I assume _most_ use-cases have 0-1 backup repositories configured, in
> the situation where you have configured multiple repositories, the v2 api
> will only permit restoring from the first one configured. (An example
> situation where this may arise is during a migration from one storage backend
> to another, or when restoring from a source that is different from where you
> will want backups to go in the future)
> This is a gap in functionality between the API versions, and I assume most
> tooling continues to utilize the v1 API at this point, but for full
> interoperability between the versions, and to support users migrating off of
> the v1 API, this parameter will need to be exposed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
