[
https://issues.apache.org/jira/browse/SOLR-15089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403911#comment-17403911
]
Andy Throgmorton commented on SOLR-15089:
-----------------------------------------
[~houston] Strictly speaking, that lib does not need to be present. If it's not
there, the AWS SDK will complain "JAXB is unavailable. Will fallback to SDK
implementation which may be less performant" but it will still function the
same. I never tested what the performance difference is, but if you're looking
for an easy solution for backporting, IMO removing that jar should be safe.
As to why v1 vs v2, it's just a relic of when we first built our plugin – v2
didn't exist yet. We've talked about migrating our internal version to v2 (to
get some cool stuff like metrics) but it hasn't been a priority for us. When we
last looked at it, pretty much all the bindings changed, so we didn't want
re-write the entire plugin in the eleventh hour.
That being said, I am very pro-v2 and think it's a good idea to migrate now
that the plugin is committed in 9.x. I'll follow that jira; please feel free to
@ me on any v2 PR you write.
> 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
> Components: contrib - S3 Repository
> Reporter: Jason Gerlowski
> Assignee: Houston Putman
> Priority: Major
> Fix For: 8.10
>
> Time Spent: 14h 40m
> 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 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...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
