[JAMES-3470] Implement CassandraEmailChangeRepository

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: 3.6.0
• Assignee: Unassigned
• Reporter: Lan Khuat
• Created: 10/Dec/20 09:24
• Updated: 14/Jan/21 03:31
• Resolved: 14/Jan/21 03:31

Description

Same purpose with the MemoryEmailChangeRepository, we now need to implement it in Cassandra.

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.

DoD

Write unit tests to show that the EmailChangeRepository is working properly.