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 2020/07/24 02:45:00 UTC
[jira] [Created] (JAMES-3318) DeletedMessageVault::deleteMessage
should call directly DumbBlobStore::delete
Benoit Tellier created JAMES-3318:
-------------------------------------
Summary: DeletedMessageVault::deleteMessage should call directly DumbBlobStore::delete
Key: JAMES-3318
URL: https://issues.apache.org/jira/browse/JAMES-3318
Project: James Server
Issue Type: Improvement
Components: Blob
Reporter: Benoit Tellier
== Why
DeletedMessage vault needs to delete related content. We need the deletion to take place immediately.
However appending into the vault is a common operation and we want to have metrics for it.
We want to keep the BlobStore API simple and easy to use.
== DOD
`DeDuplicationBlobStore::delete` is a noop.
All code for `BlobStore::delete` is moved into `PassThroughBlobStoreTest`.
DeletedMessage functionality of the DeletedMessageVault keeps unaffected.
== How
Implement `DeletedMessageVault::deleteMessage` via direct access to the DumbBlobStore.
--
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