[
https://issues.apache.org/jira/browse/JAMES-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lan Khuat updated JAMES-3470:
-----------------------------
Description:
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.
was:
Same purpose with the MemoryEmailChangeStore, 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 CassandraEmailChangeStore APIs, based on the contract that has
already been defined.
h1. DoD
Write unit tests to show that the EmailChangeStore is working properly.
Summary: Implement CassandraEmailChangeRepository (was: Implement
CassandraEmailChangeStore)
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
