Cassandra implement for CustomIdentityDAO

[quantranhong1999]

Why

This is Cassandra's implementation for CustomIdentityDAO.

Requires

• Memory IdentityRepository and contract tests

How

• Create a user defined type for email address: email_address(name TEXT, email TEXT)
• Create CassandraIdentityModule with table structure:

PK user TEXT
CK identity_id UUID
C name TEXT
C email TEXT
C replyTo set<email_address>
C bcc frozen set<email_address>
C textSignature TEXT
C htmlSignature TEXT
C mayDelete BOOLEAN

• Create CassandraCustomIdentityDAO that implement CustomIdentityDAO

DoD

Write test implement the contract and pass all test cases

[chibenwa]

set<TEXT> => frozen<set<TEXT>> we do not need to update individual elements, let's not pay the (expensive) cost of mutable collections in Cassandra...

[chibenwa]

Mono<Identity> selectOne(Username username, IdentityId id); ?

[chibenwa]

Also we should avoid leaking Mono/Flux usage in API interfaces. Please favor Publisher.

[quantranhong1999]

I changed to

C replyTo frozen map(<TEXT>, <TEXT>)
C bcc frozen map(<TEXT>, <TEXT>)

cause EmailAddress contains 2 fields

[chibenwa]

cause EmailAddress contains 2 fields

Please use a (frozen) user defined type instead (set of a user defined type if need be.)

[quantranhong1999]

Please use a (frozen) user defined type instead (set of a user defined type if need be.)

Can you tell me more about this? I am having class and can not inspect the code for more information now :')

[chibenwa]

Sure.

• 1. You need to build a type using CassandraModule. Eg: CassandraMailboxModule
• 2. Use the (frozen) type in your table definition. Note that you can do (frozen) collections of (frozen) types. Eg: CassandraMailboxModule still...
• 3. You can work with your user defined type using CassandraTypesProvider class. A good example of this could be CassandraMailboxDAO + MailboxBaseTupleUtil.