Every Cassandra table has at least one column: A column named
which stores the persistent object translated into
If the write timestamps
configuration is turned on, then
modified_timestamp columns are added. If optimistic
locking is turned on, then a
column is also added. Please note that the Cassandra optimistic
locking implementation uses lightweight
for updates and deletes, introducing an
IF row_version = ... clause
to the database command. This will incur a performance penalty.
More columns are added to support any keys or
indexes for the persistent
type. Every property used in a
key or index is expanded in to a sequence of property components that
all have basic types. These property
components are stored in Cassandra columns, and all have names
prop_. Those property components that do not belong
to your primary key are
The property component columns are used to back calls to Repo.retrieve, as well as query retrievals. Please note that queries constructed using properties that are not part of a longevity key or index will fail.
Cassandra table names are generated by underscoring the camel-cased name of the persistent class.