Provides support to increase developer productivity in Java when using Apache Cassandra. Uses familiar Spring concepts such as a template classes for core API usage and lightweight repository style data access.
Spring Data Cassandra strictly requires @Table on entities. BasicCassandraMappingContext distinguishes by @Table what entities should be treated as table entities and which ones should be user-defined types/primary keys. This distinction is only required for two uses:
Table creation
Table truncation within tests
Both cases are valid but @Table is not necessarily required for all persistent entities. Entities without @Table can be still mapped in both directions. A class annotated with @Table will participate in schema management and be exposed as a table entity. Classes used as entities without @Table can be still used to query Cassandra but schema management will not create any tables for these classes
Affects: 1.5 M1 (Ingalls), 2.0 M1 (Kay)
Issue Links:
DATACASS-86 Support basic unmapped CQL pojo query operations
Mark Paluch opened DATACASS-360 and commented
Spring Data Cassandra strictly requires
@Table
on entities.BasicCassandraMappingContext
distinguishes by@Table
what entities should be treated as table entities and which ones should be user-defined types/primary keys. This distinction is only required for two uses:Both cases are valid but
@Table
is not necessarily required for all persistent entities. Entities without@Table
can be still mapped in both directions. A class annotated with@Table
will participate in schema management and be exposed as a table entity. Classes used as entities without@Table
can be still used to query Cassandra but schema management will not create any tables for these classesAffects: 1.5 M1 (Ingalls), 2.0 M1 (Kay)
Issue Links:
Referenced from: pull request https://github.com/spring-projects/spring-data-cassandra/pull/91
Backported to: 1.5 RC1 (Ingalls)