Hi
In practice, one would want to model their data such that the 'row has
too much columns' scenario is prevented.
I am curious how really to prevent this, if the data is sharded with one
day granularity, nothing stops the client to insert enormous amount of new
columns (very often it is
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
On Fri, Apr 23, 2010 at 5:54 PM, Miguel Verde miguelitov...@gmail.comwrote:
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
