cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Cassandra Wiki] Update of "CassandraLimitations" by SilvereLestang
Date Thu, 14 Apr 2011 13:58:52 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "CassandraLimitations" page has been changed by SilvereLestang.
The comment on this change is: Adds "maximum of column per row".


  == Stuff that isn't likely to change ==
   * All data for a single row must fit (on disk) on a single machine in the cluster. Because
row keys alone are used to determine the nodes responsible for replicating their data, the
amount of data associated with a single key has this upper bound.
   * A single column value may not be larger than 2GB.
+  * The maximum of column per row is 2 billion.
  == Artifacts of the current code base ==
   * Cassandra has two levels of indexes: key and column.  But in super columnfamilies there
is a third level of subcolumns; these are not indexed, and any request for a subcolumn deserializes
_all_ the subcolumns in that supercolumn.  So you want to avoid a data model that requires
large numbers of subcolumns. is open
to remove this limitation.

View raw message