[
https://issues.apache.org/jira/browse/SOLR-15090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335608#comment-17335608
]
ASF subversion and git services commented on SOLR-15090:
--------------------------------------------------------
Commit be681bd9e0d24085c78c63fe11914faa41f4b813 in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=be681bd ]
SOLR-15090: Allow backup storage in GCS (#39)
> Allow backups to GCS (Google Cloud Storage)
> -------------------------------------------
>
> Key: SOLR-15090
> URL: https://issues.apache.org/jira/browse/SOLR-15090
> Project: Solr
> Issue Type: Sub-task
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Major
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> Solr's BackupRepository interface provides an abstraction around the physical
> location/format that backups are stored in. This allows plugin writers to
> create "repositories" for a variety of storage mediums. It'd be nice if Solr
> offered more mediums out of the box though, such as some of the "blobstore"
> offerings provided by various cloud providers.
> This ticket proposes that a "BackupRepository" implementation for Google's
> popular 'Cloud Storage' blobstore, so that Solr users can use it for backups
> without needing to write their own code.
> Google offers a GCS Java client with acceptable licensing, and the
> integration code is relatively simple. The biggest challenge in supporting
> this will likely be procedural - integration testing requires GCS access and
> GCS access costs money. We can check with INFRA to see if there is any way
> to get cloud credits for an integration test to run in nightly Jenkins runs
> on the ASF Jenkins server. Alternatively we can try to stub out the
> blobstore in some reliable way.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]