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 "René Cordier (Jira)" <se...@james.apache.org> on 2020/07/28 03:32:00 UTC

[jira] [Commented] (JAMES-3319) Actual blob deletion

    [ https://issues.apache.org/jira/browse/JAMES-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166120#comment-17166120 ] 

René Cordier commented on JAMES-3319:
-------------------------------------

[https://github.com/linagora/james-project/pull/3618] added the blob deletion in Cassandra mailbox

[https://github.com/linagora/james-project/pull/3615] added the blob deletion in CassandraMailRepository

> Actual blob deletion
> --------------------
>
>                 Key: JAMES-3319
>                 URL: https://issues.apache.org/jira/browse/JAMES-3319
>             Project: James Server
>          Issue Type: Improvement
>          Components: Blob, mailbox, MailStore &amp; MailRepository, Queue
>            Reporter: Benoit Tellier
>            Priority: Major
>
> Thanks to JAMES-3318 the deduplication blobStore delete method no longer aggressively deletes data (that could be references in another context).
> We can now safely delete data in :
>  - [ ] CassandraMailRepository
>  - [ ] Cassandra MailQueueView
>  - [ ] Cassandra mailbox (message content & attachments)
> For each usage, we need to ensure that :
>  - Data is deleted straight away on top of the passthrough blobStore
>  - Data with similar blobs being deleted have no impact when using deduplication blobStore.



--
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