[
https://issues.apache.org/jira/browse/SOLR-15089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286591#comment-17286591
]
Jason Gerlowski edited comment on SOLR-15089 at 2/18/21, 4:54 PM:
------------------------------------------------------------------
While Andy is working on cleaning up his AWS code, I wanted to get the ball
rolling on some of the bigger questions around packaging and setup. AFAIK this
(or one of the parallel tickets for GCS or Azure) will be Solr's first
"first-class" plugin (right?), so there's some things to figure out.
- *Where should the source for "first-class" plugins live?* Ishan replied to my
questions above by continuing the [mailing list
discussion|http://mail-archives.apache.org/mod_mbox/lucene-dev/202101.mbox/%3Calpine.DEB.2.21.2101141026530.13436%40slate%3E]
I referenced in my previous comment. See there for discussion.
- *Where should the project host first-class plugins from an
artifact/repository sense?* The easiest thing to do would probably be to
publish our repository of first-class plugins as a new page or pages on our
website (maybe {{/solr/plugins/downloads.html}}?)
- *What should the release process for first-class plugins look like, and how
(if at all) should it interlock with the release process for Solr proper?*
Some of this will need to flow from the ASF's release policy, but there's a lot
to figure out beyond that as well.
We don't need answers for all of these questions necessarily to close this
ticket - some could be punted to other tickets if desired. But as they'll be
eventual blockers I wanted to lay out some of the open questions here as a
start.
was (Author: gerlowskija):
While Andy is working on cleaning up his AWS code, I wanted to get the ball
rolling on some of the bigger questions around packaging and setup. AFAIK this
(or one of the parallel tickets for GCS or Azure) will be Solr's first
"first-class" plugin (right?), so there's some things to figure out.
- *Where should the source for "first-class" plugins live?* Ishan replied to my
questions above by continuing the [mailing list
discussion|http://mail-archives.apache.org/mod_mbox/lucene-dev/202101.mbox/%3Calpine.DEB.2.21.2101141026530.13436%40slate%3E]
I referenced in my previous comment. See there for discussion.
- *Where should the project host first-class plugins from an
artifact/repository sense?* The easiest thing to do would probably be to
publish our repository of first-class plugins as a new page or pages on our
website (maybe {{/solr/plugins/downloads.html}}?)
- *What should the release process for first-class plugins look like, and how
(if at all) should it interlock with the release process for Solr proper?*
Some of this will need to flow from the ASF's release policy, but there's a lot
to figure out beyond that as well
.
We don't need answers for all of these questions necessarily to close this
ticket - some could be punted to other tickets if desired. But as they'll be
eventual blockers I wanted to lay out some of the open questions here as a
start.
> 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
