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 "Rémi Kowalski (Jira)" <se...@james.apache.org> on 2020/07/27 11:36:00 UTC

[jira] [Created] (JAMES-3343) Configuration safety: disabling deduplication should not be allowed.

Rémi Kowalski created JAMES-3343:
------------------------------------

             Summary: Configuration safety: disabling deduplication should not be allowed.
                 Key: JAMES-3343
                 URL: https://issues.apache.org/jira/browse/JAMES-3343
             Project: James Server
          Issue Type: New Feature
          Components: Blob
    Affects Versions: 3.5.0
            Reporter: Rémi Kowalski
             Fix For: 3.6.0


h2. Why

Deduplication allow the use of a single object for several business entities.

Turning it off, the Duplicating blob store can, upon entity deletes, delete blobs used by other entities, jeoparadizing the data integrity of the server.

Note that enabling deduplication brings no bad consequences.
h2. DOD

 

{{Given a James server with deduplication enabled
When I reconfigure this James server and turn off deduplication
Then this James server fails}}
h2. How

Write a {{StartUpCheck}} checking this property.

Keep track of the value of "deduplication.enable" value via an event sourcing system.

The aggregate will ensure the rule that "deduplication should not be disabled", and your start up check will update the aggregate with the new configuration value, if it changed, effectively triggering the check.

Note that this ticket can be handled separately, only the final integration test requires dependency to other work



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