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 2021/01/14 03:32:00 UTC

[jira] [Closed] (JAMES-3470) Implement CassandraEmailChangeRepository

     [ https://issues.apache.org/jira/browse/JAMES-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

René Cordier closed JAMES-3470.
-------------------------------
    Fix Version/s: 3.6.0
       Resolution: Done

> Implement CassandraEmailChangeRepository
> ----------------------------------------
>
>                 Key: JAMES-3470
>                 URL: https://issues.apache.org/jira/browse/JAMES-3470
>             Project: James Server
>          Issue Type: Sub-task
>            Reporter: Lan Khuat
>            Priority: Major
>             Fix For: 3.6.0
>
>
> Same purpose with the MemoryEmailChangeRepository, we now need to implement it in Cassandra.
> h1. How
> 1. Define a EmailChange table with these fields:
>  * accountId
>  * state
>  * created
>  * updated
>  * destroyed
>  * date
> 2. Implement the CassandraEmailChangeRepository APIs, based on the contract that has already been defined.
> h1. DoD
> Write unit tests to show that the EmailChangeRepository is working properly.



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