gerlowskija opened a new pull request #39:
URL: https://github.com/apache/solr/pull/39


   # Description
   
   Solr offers a "BackupRepository" abstraction that allows users to implement 
storage to arbitrary backends.  But ootb, Solr only offers repositories for 
HDFS (deprecated) and local file system.  Users commonly want to backup data to 
the cloud-storage systems offered by popular vendors like Google, Amazon, and 
Microsoft.
   
   # Solution
   
   This PR adds a BackupRepository implementation for GCS, Google's cloud 
storage offering.  Credentials are stored on disk, in a file pointed to by an 
environment variable and a Java client provided by Google uses those 
credentials and other provided configuration to communicate with GCS.
   
   # Tests
   
   The PR contains two new tests: GCSBackupRepositoryTest and 
GCSIncrementalBackupTest.  These tests work when provided with valid GCS 
credentials.  Prior to committing they'll need to be reworked to use a 
mocked/stubbed `Storage` object.
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to 
Contribute](https://wiki.apache.org/solr/HowToContribute) and my code conforms 
to the standards described there to the best of my ability.
   - [x] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [x] I have given Solr maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended)
   - [x] I have developed this patch against the `main` branch.
   - [ ] I have run `./gradlew check`.
   - [ ] I have added tests for my changes.
   - [ ] I have added documentation for the [Reference 
Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to