You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2021/07/28 09:48:00 UTC
[jira] [Closed] (JAMES-3615) S3BlobDAO emptying bucket do not take
into account trucated bucket lists
[ https://issues.apache.org/jira/browse/JAMES-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3615.
---------------------------------
Resolution: Fixed
Solved as part of https://github.com/apache/james-project/pull/546
> S3BlobDAO emptying bucket do not take into account trucated bucket lists
> ------------------------------------------------------------------------
>
> Key: JAMES-3615
> URL: https://issues.apache.org/jira/browse/JAMES-3615
> Project: James Server
> Issue Type: Bug
> Components: Blob
> Affects Versions: 3.6.0
> Reporter: Benoit Tellier
> Priority: Minor
> Fix For: 3.7.0
>
>
> https://docs.aws.amazon.com/AmazonS3/latest/userguide/delete-bucket.html Using the AWS SDK Java clearly does a loop as long as the list of objects is truncated.
> We currently do not apply suck logic in S3BlobDAO.
> Obviously, deleting large buckets would fail as the bucket would not have had been well emptied before.
> So far only the Deleted Message Vault purge feature is impacted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org