[
https://issues.apache.org/jira/browse/SOLR-15658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625250#comment-17625250
]
Kevin Risden commented on SOLR-15658:
-------------------------------------
[~houston] I closed PR #314 since its been a while and not sure if
findify/s3mock makes sense with no commits it >3 years. Is the statement about
abobe/s3mock and the s3 client versions still true? I know adobe/s3mock has
been updated a bunch recently.
> Investigate replacing the S3Mock implementation for S3 testing
> --------------------------------------------------------------
>
> Key: SOLR-15658
> URL: https://issues.apache.org/jira/browse/SOLR-15658
> Project: Solr
> Issue Type: Sub-task
> Components: contrib - S3 Repository, Tests
> Reporter: Houston Putman
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We currently use [adobe/S3Mock|https://github.com/adobe/S3Mock], which is
> very s3 compliant, and works the same as AWS S3 in almost all use cases. The
> problem however, is that it can be slow to start up and it also requires us
> to import dependencies for old s3 client versions (v1), when we are using the
> up-to-date version (v2).
> There are other S3 Mock options, including
> [findify/s3mock|https://github.com/findify/s3mock] written in Java that can
> be used completely in-memory. While this project is not as well kept as
> Adobe's (no commits in over a year), it is worth exploring how this would
> work with our tests. (It also requires no s3 client libraries, so we can
> remove the dependency on the v1 api)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
