[
https://issues.apache.org/jira/browse/SOLR-15089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286710#comment-17286710
]
Jason Gerlowski commented on SOLR-15089:
----------------------------------------
{quote}Honestly, I feel this should just be a contrib, the same as the existing
ones. There is SOLR-14688 for discussing if we want to move to a different
strategy.
{quote}
I didn't realize there was a whole Jira for hashing this out. Thanks for the
pointer! In terms of contrib vs plugin, I'm of two minds.
The contrib approach is well trodden, easy, and reversible (contribs can be
made into plugins later). All very appealing.
But on the other hand I thought there was a certain amount of consensus about
net-new optional modules being created as plugins (and not contribs). I don't
want to go against consensus just out of convenience.
(Though maybe this consensus never existed - I spent a little time looking for
the relevant thread but couldn't find it. Even if the consensus was clear,
there's probably a good argument that the project needs more time to hash out
the SOLR-14688 questions, and that devs should continue to create contribs
until those discussions play out.)
Anyway, I'll give this some more thought.
{quote}the S3 client could just work with GCS?
{quote}
Interesting, this is news to me and I'll have to read more.
> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
