[
https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895815#comment-15895815
]
Steve Loughran commented on SOLR-9952:
--------------------------------------
# use s3a:// over s3n://, as s3a is maintained, way better these days, bug
reports will be looked at. etc/
# so you can drop jets3t as a dependency: s3a depends on the AWS lib, and a
version of jackson compatible with it (key troublespot there).
I don't know enough about your test runner to understand the tests properly,
but I don't seen anything to run away from. Do bear in mind that listings can
take time to be consistent with your writes to s3; always good for the tests to
spin & sleep awaiting their final state, rather than give up immediately
> S3BackupRepository
> ------------------
>
> Key: SOLR-9952
> URL: https://issues.apache.org/jira/browse/SOLR-9952
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mikhail Khludnev
> Attachments:
> 0001-SOLR-9952-Added-dependencies-for-hadoop-amazon-integ.patch,
> 0002-SOLR-9952-Added-integration-test-for-checking-backup.patch,
> core-site.xml.template, Running Solr on S3.pdf
>
>
> I'd like to have a backup repository implementation allows to snapshot to AWS
> S3
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
