Tables in Apache Cassandra

Because tables in Apache Cassandra are very similar to the tables of relational databases, this article describing them won't focus on basic points. Instead, we'll explore more Cassandra specific subjects, such as configuration or different types.

Looking for a better data engineering position and skills?

You have been working as a data engineer but feel stuck? You don't have any new challenges and are still writing the same jobs all over again? You have now different options. You can try to look for a new job, now or later, or learn from the others! "Become a Better Data Engineer" initiative is one of these places where you can find online learning resources where the theory meets the practice. They will help you prepare maybe for the next job, or at least, improve your current skillset without looking for something else.

👉 I'm interested in improving my data engineering skillset

See you there, Bartosz

The first part of the article describes some options which can be assigned to tables in Apache Cassandra. The second part list some particularities of tables. The last part shows how to implement that through Java API.

Table configuration in Cassandra

Sometimes (very often?) CREATE TABLE is not a simple definition of columns to create. In additional it takes some configuration properties which should be defined after columns, through WITH clause:

CREATE TABLE my_table (...columns here) 
  WITH config_entry1 = value1 AND config_entry2 = value2

As you can see already, there are no single one option available. Instead, we can configure following properties (non exhaustive list):

Table particularities

Some of table features are very specific to Cassandra. The first one are static column. By making a column static we associate it to all values having the same partition key. As usual, only non PRIMARY KEY columns can be static. An additional constraint is that a table without clustering columns can't have static columns. In this case, each partition has only 1 row and automatically each column is static. To declare static column, the operation consists on append "static" word after column type definition.

Another specific tool are functions. The first one concerns the time of values definition. Thanks to WRITETIME(column_name) we can discover when given value was defined. When we want to work with paged results, Cassandra provides a special function TOKEN(value). It makes possible to page when unordered partitioners (RandomPartitioner and Murmur3Partitioner) are used. In this case, the comparison is not made on stored values but on tokens generated by this function.

The 3rd special Cassandra feature are user-defined types. It allows to construct customized data types to be use further for table columns definitions. The definition of this data type can be done with CREATE TYPE query.

Example of table creation in Cassandra Java API

Test cases are quite short this time. They present the use and the particularity of static columns, table creation with options and writetime function:

public void should_correctly_create_table_from_java_api() {
  Statement createStatement = SchemaBuilder.createTable("customer")
    .addPartitionKey("id", DataType.text())
    .addClusteringColumn("login", DataType.text())
    .addClusteringColumn("age", DataType.smallint())
    .withOptions().clusteringOrder("login", SchemaBuilder.Direction.DESC)
    .comment("test comment").gcGraceSeconds(2);

  KeyspaceMetadata ks = CLUSTER.getMetadata().getKeyspace("tableTest");
  TableMetadata table = ks.getTable("customer");

  assertThat(table.getClusteringColumns()).extracting("name").containsOnly("login", "age");
  assertThat(table.getOptions().getComment()).isEqualTo("test comment");

public void should_correctly_work_with_static_column() {
  // To test if static column really work, first we create the rows
  // representing 1 players of a same team
  // After we INSERT new player under the same partition key but
  // with different value for static column with division
  // When we read the data after the change, modified column should
  // have new values for both rows (only 1 was explicitly edited)

  // However, the case doesn't work with update for this flow:
  // 1/ Create 2 players for the same partition key
  // 2/ Update static column for one of them
  // Expected error should be in this case:
  // Invalid restrictions on clustering columns since the UPDATE statement modifies only static columns
  String team = "RC Lens";
  int foundationYear = 1906;
  String country = "FR";
  int division = 2;
  SESSION.execute("INSERT INTO static_team_player (teamName, player, foundationYear, country, division) " +
    " VALUES (?, ?, ?, ?, ?)", team, "Player_1", foundationYear, country, division);

  ResultSet result = SESSION.execute("SELECT * FROM static_team_player");
  List<Row> rows = result.all();

  // Now, add row with Player_2
  SESSION.execute("INSERT INTO static_team_player (teamName, player, foundationYear, country, division) " +
    " VALUES (?, ?, ?, ?, ?)", team, "Player_2", foundationYear, country, 1);

  result = SESSION.execute("SELECT * FROM static_team_player");
  rows = result.all();
  assertThat( -> r.getString("teamName"))).containsOnly(team);
  assertThat( -> r.getString("player"))).containsOnly("Player_1", "Player_2");
  assertThat( -> r.getInt("foundationYear"))).containsOnly(foundationYear);
  assertThat( -> r.getInt("division"))).containsOnly(1);

public void should_correctly_get_write_time_of_a_column() {
  long insertTime = System.currentTimeMillis();
  SESSION.execute("INSERT INTO static_team_player (teamName, player, foundationYear, country, division, bornYear) " +
    " VALUES ('Team1', 'Player1', 1999, 'BE', 1, 1980)");

  ResultSet writetimeResult = SESSION.execute("SELECT bornYear, WRITETIME(country) AS countryCreationTime FROM static_team_player " +
    " WHERE teamName = 'Team1' AND player = 'Player1'");


The article describes several features for Cassandra tables. The first part presents options available during table creation. They concern things like compaction, compression, tombstone keeping time. The second part concerns points related more to reading stuff, such as functions, customized data types or special kind of static columns. The last part presents described cases through JUnit tests.

If you liked it, you should read:

📚 Newsletter Get new posts, recommended reading and other exclusive information every week. SPAM free - no 3rd party ads, only the information about waitingforcode!