One would use batch processes (e.g. through Hadoop) or client-side aggregation, yes. In theory it would be possible to introduce runtime sharding across rows into the Cassandra server side, but it's not part of its design.

In practice, one would want to model their data such that the 'row has too much columns' scenario is prevented.

On May 4, 2010, at 8:06 AM, Даниел Симеонов <> wrote:

Hi Miguel,
  I'd like to ask is it possible to have runtime sharding or rows in cassandra, i.e. if the row has too much new columns inserted then create another one row (let's say if the original timesharding is one day per row, then we would have two rows for that day). Maybe batch processes could do that. 
Best regards, Daniel.

2010/4/24 Miguel Verde <>
TimeUUID's time component is measured in 100-nanosecond intervals. The library you use might calculate it with poorer accuracy or precision, but from a storage/comparison standpoint in Cassandra millisecond data is easily captured by it.

One typical way of dealing with the data explosion of sampled time series data is to bucket/shard rows (i.e. Bob-20100423-bloodpressure) so that you put an upper bound on the row length.

On Apr 23, 2010, at 7:01 PM, Andrew Nguyen <> wrote:


I am looking to store patient physiologic data in Cassandra - it's being collected at rates of 1 to 125 Hz.  I'm thinking of storing the timestamps as the column names and the patient/parameter combo as the row key.  For example, Bob is in the ICU and is currently having his blood pressure, intracranial pressure, and heart rate monitored.  I'd like to collect this with the following row keys:


The column names would be timestamps but that's where my questions start:

I'm not sure what the best data type and CompareWith would be.  From my searching, it sounds like the TimeUUID may be suitable but isn't really designed for millisecond accuracy.  My other thought is just to store them as strings (2010-04-23 10:23:45.016).  While I space isn't the foremost concern, we will be collecting this data 24/7 so we'll be creating many columns over the long-term.

I found which states that the entire row must fit in memory.  Does this include the values as well as the column names?

In considering the limits of cassandra and the best way to model this, we would be adding 3.9 billion rows per year (assuming 125 Hz @ 24/7).  However, I can't really think of a better way to model this...  So, am I thinking about this all wrong or am I on the right track?