caelcs / cassitory Goto Github PK

Have in mind the option of converting this project to a multi module project.

In the scenario where your DTO and the cassandra entities has the same field name then Mapping annotation should take that as default unless that we define something else.

The goal here is for the repository to provide a way to run queries an populate the pojo again.

With the base repository available now the processor can generate automatically the repository for the DTO.

In the case of migration of tables... it would be nice to have a way to decide whether to write to both tables and then later on write to one driven only by config...
Eventually when the old tables is ready to be deleted then the reference can be removed from Cassitory annotations.

It would be nice to generate integration test for the Repository and see if there is any typo in the queries or mapping.
One way to do this is by using test annotation processor that would generate all the tests but it would need Cassandra unit as dependency.

Two topics very related each other.

• First one is to provide a way to validate that the parameters and query are correct against cassandra.

• Second is to support lazy initialisation to create the prepared statements knowing that the session can or not be available. This is particularly useful when you use a DI framework and your session is not ready when the application context has finished but you don't want you application not to start because of it.

Evaluate the possibility of supporting queries and populate the DTO with the result coming from the target table.