[
https://issues.apache.org/jira/browse/SOLR-15089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286717#comment-17286717
]
Ishan Chattopadhyaya commented on SOLR-15089:
---------------------------------------------
I am uncomfortable with this being a "contrib" in the lucene-solr repository
for the following reasons:
# I don't want bloat in the main repository with code that is clearly optional
to the search engine. solr-sandbox or solr-extras is better, IMHO.
# I don't want to see flurry of JIRAs, PRs, comments etc. for the main
repository dealing with fringe issues to do with S3 or GCS or Azure Blobstore
etc. It is a distraction.
# A PR for this "contrib" could include change to other important modules, and
I want us to not be able to do so, without going in everytime and looking into
the PRs.
# I don't want to be blocked on committing something to the main repository,
just because it breaks tests in s3mock, S3 support etc.
And of course, I don't want such things being shipped by default (and today all
contribs are shipped with Solr).
> Allow backup/restoration to Amazon's S3 blobstore
> --------------------------------------------------
>
> Key: SOLR-15089
> URL: https://issues.apache.org/jira/browse/SOLR-15089
> Project: Solr
> Issue Type: Sub-task
> Reporter: Jason Gerlowski
> Priority: Major
>
> 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 Amazon's
> popular 'S3' blobstore, so that Solr users can use it for backups without
> needing to write their own code.
> Amazon offers a s3 Java client with acceptable licensing, and the required
> code is relatively simple. The biggest challenge in supporting this will
> likely be procedural - integration testing requires S3 access and S3 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]
