Entity Mapper Add-on for the DataStax Java Driver (Driver) for Cassandra (C*).
This Add-on allows you to synchronize schema automatically and persist JPA annotated entities in C*.
No mapping files, no scripts, no configuration files.
No need to create Tables and Indexes for your Entity manually.
Entity definition will be automatically synchronized with C* .
Add-on is not replacement for the Driver but lightweight Object Mapper on top of it.
You still can utilize full power of the Driver API and Datastax documentation.
Mapping Add-on relies on JPA 2.1 and Driver 2.1 (which means support for Cassandra 2, Binary Protocol and CQL3)
IMPORTANT!!!
Starting ver 2.1.0 Datastax released simple Object Mapping API.
If you are curious which one to start with you must read My Mapper vs Datastax Mapper.
If after reading you still don’t have opinion which one to go with you better stick to Datastax Mapper.
And if you feel the pain using it please come back and try out mine.
[More Usage Samples in Unit Tests] (https://github.com/valchkou/cassandra-driver-mapping/blob/master/src/test/java/com/datastax/driver/mapping/)
[Spring Framework Example] (https://github.com/valchkou/SpringFrameworkCassandraSample)
- Features
- Jump Start
- Mapping Session API
- Various Mappings
- Optimistic Lock
- Nested Entities
- Under The Hood
- My Mapper vs Datastax Mapper
The features provided by the module include:
-
Object Mapper
- Get, Save, Delete entity. (Synchronous and Asynchronous).
- Update individual value. (Synchronous and Asynchronous).
- Batch Save/Delete. (Synchronous and Asynchronous).
- Run and Map custom Queries and ResultSets.
- Versioning and Optimistic Concurrency control.
- Direct Collections Modifications
-
Schema Sync
- Automatically create table and indexes from Entity.
- Automatically Alter table and indexes if entity definition has changed.
- Drop table.
- Generate Script.
Session session; // initialize datastax session.
MappingSession mappingSession = new MappingSession("keyspace_name", session);
If you wish your mapping session do not synchronize your entities with C* you may turn synch off:
```java
MappingSession mappingSession = new MappingSession("keyspace_name", session, true);
// OR
MappingSession mappingSession = new MappingSession("keyspace_name", session);
mappingSession.setDoNotSync(true);
Underlying Datastax Session does all the heavylifting and is expansive.
Prior using MappingSession you need to open the Datastax Session and create the Keyspace using the standard Datastax Driver API. If you are not familiar with procedure please refer to Datastax Dcumentation.
Or look at the Spring Framework Example.
- Get.
Entity entity = mappingSession.get(Entity.class, id);- Delete.
mappingSession.delete(entity); More samples below:
#### Write - Synchronous. ```java /** Persist Entity */ save(entity);/** Persist Entity with WriteOptions*/
save(entity, writeOptions);
/** Remove an item or items from the Set or List. */
remove(id, Entity.class, propertyName, item);
/** Append value to the Set, List or Map. Value can be a single value, a List, Set or a Map. */
append(id, Entity.class, propertyName, value);
/** Append value to the Set, List or Map with WriteOptions. Value can be a single value, a List, Set or a Map. */
append(id, Entity.class, propertyName, value, writeOptions);
/** Save Individual Value. */
updateValue(id, Entity.class, propertyName, value);
/** Save Individual Value with WriteOptions. */
updateValue(id, Entity.class, propertyName, value, writeOptions);
/** Place value at the beginning of the List.
* Value can be a single value or a List. */
prepend(id, Entity.class, propertyName, value);
/** Place value at the beginning of the List with WriteOptions.
* Value can be a single value or a List. */
prepend(id, Entity.class, propertyName, value, writeOptions);
/** Replace item at the specified position in the List. */
replaceAt(id, Entity.class, propertyName, item, index);
/** Replace item at the specified position in the List with WriteOptions. */
replaceAt(id, Entity.class, propertyName, item, index, writeOptions);
- Asynchronous.
All async methods run by datastax session.executeasync() and Datastax ResultSetFuture is returned.
```java
/** Asynchronously Persist Entity */
saveAsync(entity);
/** Asynchronously Persist Entity with WriteOptions */
saveAsync(entity, writeOptions);
/** Asynchronously Remove an item or items from the Set or List. */
removeAsync(id, Entity.class, propertyName, item);
/** Asynchronously Append value to the Set, List or Map. Value can be a single value, a List, Set or a Map. */
appendAsync(id, Entity.class, propertyName, value);
/** Asynchronously Append value to the Set, List or Map with WriteOptions. Value can be a single value, a List, Set or a Map. */
appendAsync(id, Entity.class, propertyName, value, writeOptions);
/** Asynchronously Save Individual Value. */
updateValueAsync(id, Entity.class, propertyName, value);
/** Asynchronously Save Individual Value with WriteOptions. */
updateValueAsync(id, Entity.class, propertyName, value, writeOptions);
/** Asynchronously Place value at the beginning of the List.
* Value can be a single value or a List. */
prependAsync(id, Entity.class, propertyName, value);
/** Asynchronously Place value at the beginning of the List with WriteOptions.
* Value can be a single value or a List. */
prependAsync(id, Entity.class, propertyName, value, writeOptions);
/** Asynchronously Replace item at the specified position in the List. */
replaceAtAsync(id, Entity.class, propertyName, item, index);
/** Asynchronously Replace item at the specified position in the List with WriteOptions. */
replaceAtAsync(id, Entity.class, propertyName, item, index, writeOptions);
Entity entity = new Entity();
entity = mappingSession.save(entity, options);
```java
import com.datastax.driver.mapping.option.WriteOptions;
...
Entity entity = new Entity();
ResultSetFuture f = mappingSession.saveValueAsync(entity, new WriteOptions().setTtl(300));
// append item to be expired in 5 sec mappingSession.append(id, Entity.class, "cats", "Expired Cat", new WriteOptions().setTtl(5));
// prepend item mappingSession.prepend(id, Entity.class, "cats", "First Cat");
// replace item at specified index mappingSession.replaceAt(id, Entity.class, "cats", "Grey Cat", 1);
// append List of items List addCats = new ArrayList(); addCats.add("Red Cat"); addCats.add("Green Cat"); mappingSession.append(id, Entity.class, "cats", addCats);
// remove item mappingSession.remove(id, Entity.class, "cats", "Grey Cat");
// remove List of items List removeCats = new ArrayList(); removeCats.add("Red Cat"); removeCats.add("Green Cat"); mappingSession.remove(id, Entity.class, "cats", removeCats);
// remove all items mappingSession.deleteValue(id, Entity.class, "cats");
<a name="collections_set"/>
- Set operations
```java
// append item
mappingSession.append(id, Entity.class, "dogs", "Black Dog");
// append item to be expired in 5 sec
mappingSession.append(id, Entity.class, "dogs", "Expired Dog", new WriteOptions().setTtl(5));
// append Set of items
Set<String> addDogs = new HashSet<String>();
addDogs.add("Red Dog");
addDogs.add("Green Dog");
mappingSession.append(id, Entity.class, "dogs", addDogs);
// remove item
mappingSession.remove(id, Entity.class, "dogs", "Black Dog");
// remove Set of items
Set<String> removeDogs = new HashSet<String>();
removeDogs.add("Red Dog");
removeDogs.add("Green Dog");
mappingSession.remove(id, Entity.class, "dogs", removeDogs);
// remove all items
mappingSession.deleteValue(id, Entity.class, "dogs");
/** append items to be expired in 5 sec */ Map<String, BigInteger> pets = new HashMap<String, BigInteger>(); pets.put("Green Dogs", 25); pets.put("Brown Cats", 50); mappingSession.append(id, Entity.class, "pets", pets, new WriteOptions().setTtl(5));
/** remove all items */ mappingSession.deleteValue(id, Entity.class, "pets");
<a name="read"/>
#### Read
```java
/** Get Entity by Id(Primary Key) */
Entity e = mappingSession.get(Entity.class, id);
/** Get Entity by Id(Primary Key) with Options */
Entity e = mappingSession.get(Entity.class, id, readOptions);
/** Get Collection of Entities by custom Query Statement */
List<Entity> list = mappingSession.getByQuery(Entity.class, queryStatement);
/** Get Collection of Entities by custom Query String */
List<Entity> list = mappingSession.getByQuery(Entity.class, queryString);
/** Convert custom ResultSet into Collection of Entities */
List<Entity> list = mappingSession.getFromResultSet(Entity.class, resultSet);
/** Convert Row of ResultSet into Entity instance. */
Entity e = mappingSession.getFromRow(Entity.class, row);
/** Convert Rows of ResultSet into Collection of Entities. */
List<Entity> list = mappingSession.getFromRows(Entity.class, rows);
Entity entity = mappingSession.get(Entity.class, id, options);
<a name="queries_mapping"/>
- Custom Queries.
This section describes how to use your Custom Queries with the Mapping Module.
There are two ways to run and map Custom Query
1) run using mapping session
```java
import com.datastax.driver.mapping.MappingSession;
...
List<Entity> result = mappingSession.getByQuery(Entity.class, query);
- run using DataStax session and map the ResultSet
import com.datastax.driver.core.Session;
import com.datastax.driver.core.ResultSet;
import com.datastax.driver.mapping.MappingSession;
...
ResultSet rs = session.execute(query);
List<Entity> result = mappingSession.getFromResultSet(Entity.class, rs);Section below describes how you can build Custom Queries.
- CQL String
import com.datastax.driver.mapping.MappingSession;
...
// build query
String query = "SELECT name, age, birth_date, salary FROM person");
// run query
List<Entity> result = mappingSession.getByQuery(Entity.class, query); - QueryBuilder (Better)
Datastax Driver shipped with a tool to build CQL statement.
You can build your query with Datastax QueryBuilder and map ResultSet on Entity.
QueryBuilder ensures you build correct CQL.
import com.datastax.driver.core.Statement;
import com.datastax.driver.core.querybuilder.QueryBuilder;
import com.datastax.driver.mapping.MappingSession;
...
// build query
Statement query = QueryBuilder.select().all().from("your_keyspace", "your_table").where(eq("column", value));
// run query
List<Entity> result = mappingSession.getByQuery(Entity.class, query);- QueryBuilder with EntityMetadata (Even Better)
In early stages you may often change table and column names.
To avoid changing queries each time you rename something you can employ entity metadata.
import com.datastax.driver.core.Statement;
import com.datastax.driver.core.querybuilder.QueryBuilder;
import com.datastax.driver.mapping.MappingSession;
import com.datastax.driver.mapping.EntityFieldMetaData;
import com.datastax.driver.mapping.EntityTypeMetadata;
...
// get Entity Metadata
EntityTypeMetadata emeta = EntityTypeParser.getEntityMetadata(Entity.class);
// get field metadata by property/field name
EntityFieldMetaData fmeta = emeta.getFieldMetadata(field_name);
// build query.
Statement query = QueryBuilder.select().all()
.from("your_keyspace", emeta.getTableName()).where(eq(fmeta.getColumnName(), value));
// run query
List<Entity> result = mappingSession.getByQuery(Entity.class, query);/** Delete Entity by ID(Primary key) */
delete(Entity.class, id);
/** Asynchronously delete Entity */
deleteAsync(entity);
/** Asynchronously Delete Entity by ID(Primary key) */
deleteAsync(Entity.class, id);
/** Delete Individual Value */
deleteValue(id, Entity.class, propertyName);
/** Asynchronously Delete Individual Value */
deleteValueAsync(id, Entity.class, propertyName);
<a name="batch"/>
### Batch
```java
mappingSession.withBatch()
.save(entityA)
.save(entityB, writeOptions)
.delete(entityD)
.execute();
ResultSetFuture f = mappingSession.withBatch()
.save(entityA)
.save(entityB, writeOptions)
.delete(entityD)
.executeAsync();IMPORTANT!!!
- Each persistant field MUST have publlic Getter/Setter.
- If entity or field is not annotated it will provide its name as default.
- Id field is required and must be annotated with @Id or @EmbeddedId.
- Index name must be unique within the keyspace.
- C* supports only single-column-index.
@Table (name="mytable") public class Entity {
@Id
private long Id;
@Column(name = "myname")
private String name;
// @Column is not required
private int age;
@Transient
private BigDecimal calculable;
// public getters/setters ...
}
CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.mytable (id bigint, myname text, age int, PRIMARY KEY(id))
<a name="mapping_index"/>
#### Mapping Indexes
```java
import javax.persistence.Id;
import javax.persistence.Table;
import javax.persistence.Column
import javax.persistence.Index
import java.util.UUID
@Table (name="mytable",
indexes = {
@Index(name="entity_email_idx", columnList="email" ),
@Index(name="entity_name_idx", columnList="myname" )
})
public class Entity {
@Id
private java.util.UUID code;
@Column(name = "myname")
private String name;
private String email;
// public getters/setters ...
}
CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.mytable (code uuid, myname text, email text, PRIMARY KEY(code));
CREATE INDEX IF NOT EXISTS entity_email_idx ON ks.mytable(email);
CREATE INDEX IF NOT EXISTS entity_name_idx ON ks.mytable(myname);
import javax.persistence.Table; import javax.persistence.EmbeddedId;
@Table(name="entity") public class Entity { @EmbeddedId private CompositeKey key; private String email; // public getters/setters ... }
CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.entity (name text, rank int, email text, PRIMARY KEY(name, rank))
<a name="mapping_partition"/>
#### Composite Partition Key
```java
public class PartitionKey {
private String firstName;
private String lastName;
// public getters/setters ...
}
public class CompositeKey {
@EmbeddedId
private PartitionKey key;
private int age;
// public getters/setters ...
}import javax.persistence.Table;
import javax.persistence.EmbeddedId;
@Table(name="entity")
public class Entity {
@EmbeddedId
private CompositeKey key;
private String email;
// public getters/setters ...
}CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.entity (firstname text, lastname text, age int, email text, PRIMARY KEY((firstname, lastname), age))
import com.datastax.driver.mapping.annotation.TableProperties; import com.datastax.driver.mapping.annotation.TableProperty;
@Table (name="mytable") @TableProperties(values = { @TableProperty("comment='Important records'"), @TableProperty("read_repair_chance = 1.0"), @TableProperty("compression ={ 'sstable_compression' : 'DeflateCompressor', 'chunk_length_kb' : 64 }") }) public class Entity {
@Id
private long Id;
private String name;
// public getters/setters ...
}
CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.mytable (id bigint, name text, PRIMARY KEY(id)) WITH comment='Important records' AND read_repair_chance = 1.0 AND compression ={ 'sstable_compression' : 'DeflateCompressor', 'chunk_length_kb' : 64 }
- Clustering Order
```java
public class CompositeKey {
private String name;
private int rank;
// public getters/setters ...
}
import javax.persistence.Table;
import javax.persistence.EmbeddedId;
import com.datastax.driver.mapping.annotation.TableProperties;
import com.datastax.driver.mapping.annotation.TableProperty;
@Table(name="entity")
@TableProperties(values = {
@TableProperty("CLUSTERING ORDER BY (rank DESC)")
})
public class Entity {
@EmbeddedId
private CompositeKey key;
private String email;
// public getters/setters ...
}CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.entity (name text, rank int, email text, PRIMARY KEY(name, rank)) WITH CLUSTERING ORDER BY (rank DESC)
@Table (name="mytable") public class Entity {
@Id
@Column(name="uid", columnDefinition="timeuuid") // case insensitive
private UUID uid;
@Column(name="name", columnDefinition="VarChaR") // case insensitive
private String name;
// public getters/setters ...
}
CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.mytable (uid timeuuid, name varchar, PRIMARY KEY(uid))
<a name="mapping_mixed"/>
#### Mixed Case for Column Names
[C* converts all names to lowercase](http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/ucase-lcase_r.html). This is default and recommended approach.
But in case you need enforce the case you will need to wrap you names in double quotes.
```java
import javax.persistence.Id;
import javax.persistence.Table;
import javax.persistence.Column
@Table (name="mytable")
public class Entity {
@Id
@Column(name = "\"KEY\"")
private int id;
private String firstName;
@Column(name = "\"last_NAME\"")
private String lastName;
@Column(name = "AGE")
private int age;
// public getters/setters ...
}
CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.mytable ("KEY" int, firstName text, "last_NAME" text, AGE int, PRIMARY KEY("KEY"))
Collections must have generic type defined. Only java.util.List, Map and Set are allowed.
By default implementation of HashMap, HashSet and ArrayList are used.
@Table (name="entity")
public class Entity {
...
private List<String> cats;
private Set<Date> dogs;
private Map<String, BigInteger> pets;
...
}If you are unhappy with defaults and would like your data to be baked with specific collection implementation you can apply an annotation as shown below.
NOTE: this is strictly java side feature and does not effect how your data stored in C*.
import com.datastax.driver.mapping.annotation.CollectionType;
...
@Table (name="entity")
public class Entity {
...
@CollectionType(LinkedList.class)
private List<String> cats;
@CollectionType(TreeSet.class)
private Set<Date> dogs;
@CollectionType(TreeMap.class)
private Map<String, BigInteger> pets;
...
}CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.entity (id uuid, cats list<text>, dogs set<timestamp>, pets map<text, varint>, PRIMARY KEY(id))
For more info on collections please refer [Datastax Using Collection] (http://www.datastax.com/documentation/cql/3.1/cql/cql_using/use_collections_c.html)
#### TTL ```java import com.datastax.driver.mapping.annotation.Ttl; ... @Ttl(300) // expires in 5 minutes @Table (name="mytable") public class Entity { ... } ``` This is TTL for the entity will be applied whenever entity of this type is saved. NOTE: @Ttl does not set table property: 'default_time_to_live'. You can set default with [@TableProperty](#mapping_properties) Also you can override @TTL or default_time_to_live at the time you save entity as: ```java mappingSession.save(entity, new WriteOptions().setTtl(600)); // expires in 10 minutes ``` #### Static columns [what is it?](http://www.datastax.com/dev/blog/cql-in-2-0-6)import com.datastax.driver.mapping.annotation.Static;
...
@Table (name="mytable")
public class Entity {
@EmbeddedId
private ClusteringKey key;
@Static
private long balance;
...
}public class ClusteringKey {
private String user;
private int expense_id;
...
}CQL3 Statement
CREATE TABLE IF NOT EXISTS ks.mytable (user text, expense_id int, balance bigint static, PRIMARY KEY(user, expense_id))
import javax.persistence.Id;
import javax.persistence.Table;
import javax.persistence.Version;
@Table(name="entity")
public class EntityWithVersion {
@Id
private java.util.UUID id;
@Version
private long version;
// public getters/setters ...
}
@Test
public void entityWithVersionTest() throws Exception {
UUID id = UUID.randomUUID();
EntityWithVersion obj = new EntityWithVersion();
obj.setId(id);
obj.setName("ver1");
EntityWithVersion loaded = mappingSession.get(EntityWithVersion.class, id);
assertNull(loaded);
// save object ver1
EntityWithVersion saved = mappingSession.save(obj);
// get object ver1
EntityWithVersion obj1 = mappingSession.get(EntityWithVersion.class, id);
assertEquals(obj1, saved);
assertEquals(1, saved.getVersion());
// save object ver2
saved = mappingSession.save(saved);
EntityWithVersion obj2 = mappingSession.get(EntityWithVersion.class, id);
assertEquals(obj2, saved);
assertEquals(2, saved.getVersion());
saved = mappingSession.save(obj1);
assertNull(saved);
}
<a name="nested"/>
### Nested Entities
Cussandra does not support nested entities nor it has integrity constraints.
So there is no automatic support for nested entities.
This Section describes how you can support Nested entities manually.
```java
@Table(name="entity_a")
public class EntityA {
@Id
private UUID id;
// public getters/setters ...
}
@Table(name="entity_b")
public class EntityB {
@Id
private UUID id;
// reference on EntityA
private UUID refA;
// public getters/setters ...
}
public class TestNested() {
@Test
public void saveNested() throws Exception {
EntityA a = new EntityA();
mappingSession.save(a);
EntityB b = new EntityB();
b.setRefA(a.getId());
mappingSession.save(b);
}
@Test
public void loadNested() throws Exception {
UUID bId = some_id;
EntityB b = mappingSession.load(bId);
EntityA a = mappingSession.load(b.getRefA());
}
}
If you want to tune the cache for better performance you can do it as:
Cache<String, PreparedStatement> cache = CacheBuilder
.newBuilder()
.expireAfterAccess(60, TimeUnit.MINUTES)
.maximumSize(10000)
.concurrencyLevel(8)
.build();
MappingSession.setStatementCache(cache); // create or alter
import com.datastax.driver.mapping.schemasync.SchemaSync;
...
SchemaSync.sync(keyspace, session, Entity.class); // drop table
import com.datastax.driver.mapping.schemasync.SchemaSync;
...
SchemaSync.drop(keyspace, session, Entity.class);// get CQL script which will be generated and run
import com.datastax.driver.mapping.schemasync.SchemaSync;
...
String script = SchemaSync.getScript(keyspace_name, datastax_session, Entity.class);// get CQL script which will be generated and run
import com.datastax.driver.mapping.schemasync.SchemaSync;
...
String script = SchemaSync.getScript(keyspace_name, datastax_session, Entity.class);You don't need to use this API unless you have reasons.
Such as unittests or if you want to gain few milliseconds on the first use
you may want to invoke the synchronization on the application start up instead.
As the project is evolving sometimes there is need to refactor entity, add or delete properties and indexes.
Again this all taken care automatically but with certain restrictions.
Please read to understand what will and will not be altered and synchronized.
Not Alterable
- add/delete/rename primary key columns. (C* restriction)
- change column data type to incompatible one, such as string to number. (C* restriction)
- change property name which is not annotated as @Column. This will be understood as a new property.
- Table Properties (@TableProperties). There is no consistent way to compare with existing properties.
Alterable
- add new property.
- delete property.
- add index on column.
- change datatype to compatible one. Compatibility is enforced by C*.
You may want to access Entity metadata if you are building custom Statements.
Entity Metadata contains corresponding table and column names.
Entity Metadata can be easily accessed anywhere in your code as:
EntityTypeMetadata emeta = EntityTypeParser.getEntityMetadata(Entity.class)
emeta.getTableName(); // corresponding table name in C*
// get field meta info by property name
EntityFieldMetaData fdata = emeta.getFieldMetadata("email");
// corresponding column name in C*
String columnName = fdata.getColumnName();
// all the persistent fields on entity
List<EntityFieldMetaData> fields = emeta.getFields();Datastax driver has mapping of datastax types to java. But not all types are mapped as 1-to-1.
CQL3 data types to Java types
In order the mapping to work the module defines backward mapping for the types.
| Java type | CQL3 data type |
|---|---|
| int | int |
| long | bigint |
| float | float |
| double | double |
| boolean | boolean |
| java.lang.Double | double |
| java.nio.ByteBuffer | blob |
| java.math.BigDecimal | decimal |
| java.lang.String | text |
| java.util.Date | timestamp |
| java.lang.Boolean | boolean |
| java.lang.Integer | int |
| java.lang.Long | bigint |
| java.util.Map | map |
| java.lang.Float | float |
| java.util.Set | set |
| java.math.BigInteger | varint |
| java.util.UUID | uuid |
| java.util.List | list |
You can override defaults as:
import com.datastax.driver.core.DataType;
...
Map<Class<?>, DataType.Name> mapping = new HashMap<Class<?>, DataType.Name>();
.... populate the map
EntityTypeParser.setDataTypeMapping(mapping);Or override individual type:
import com.datastax.driver.core.DataType;
...
EntityTypeParser.overrideDataTypeMapping(javaClass, DataType.Name)Both mappers built on top of Datastax Java Driver and introduce Object Mapper layer for simplicity. There are few common features and differences. You can read about them below.
To me the biggest difference so far is that datastax mapper does not generate schema for you automatically. You will have to manually create tables, indexes and manually alter schema if you make any changed down the road. I am surprised Datastax missed it. This is MUST-HAVE feature for modern ORM.
Frankly speaking auto synch is mainly why I started my project. I got sick of preparing and running scripts whenever I was adding property or entity. I came up with SchemaSync and the next logical step was the mapper. I applied my best efforts to make it simple and straightforward.
Autosync is not only difference. There are few more:
Datastax documentation on their Mapper is very shallow.
Datastax mapper needs to be instantiated for each entity class. If you have 20 entity classes you will create 20 mappers.
Mapper<Account> mapper = new MappingManager(session).mapper(Account.class);
My mapper is not bound to an entity. You can have just one or 20 – it’s up to you.
MappingSession mapper = new MappingSession("keyspace_name", session);
Datastax PK fields are all declared within entity class:
@Table(keyspace = "ks", name = "test_table")
public static class TestTable {
@PartitionKey(0)
private int pk1;
@PartitionKey(1)
private int pk2;
@ClusteringColumn(0)
private int cc1;
@ClusteringColumn(1)
private int cc2;
}
My mapper PK is more of JPA/Hibernate style with @Id and @EmbeddedId. Sample here
Support for collection operations
This feature is provided by Java Driver, CQL3 and Cassandra. But not by Datastax Mapper.
Supported by My Mapper: Samples here
Datstax mapper does not support optimistic concurrency.
My module supports it with @Version annotation
Datastax proposes Accessor class which incapsulates all the custom queries for the given Entity class.
My mapper can eat your custom Queries and ResultSets and convert them into any entities with no extra wrappers and handlers. Sample here
This feature is not exists in Datastax Mapper. Basically you can map any ResultSet from any table on any Entity with My Mapper.
This feature is missing in datastax mapper.
You will have to manually create tables, indexes and manually alter schema.
create datastax session and pass it into the mapper instance.
Their Maven artifact magically matches mine. But be aware it’s not the same!
GroupId is different, Be sure you use correct one.
MINE:
<dependency>
<groupId>com.valchkou.datastax</groupId>
<artifactId>cassandra-driver-mapping</artifactId>
</dependency>
DATASTAX:
<dependency>
<groupId>com.datastax.cassandra</groupId>
<artifactId>cassandra-driver-mapping</artifactId>
</dependency>
Underlying conversation mechanisms with Cassandra are the same.
Both annotation driven and do not require configuration or mapping files.