ially, one table would serve as an index to the
other, which is the data store. I have a working application that's
structured like that and it works OK.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/help-modeling-a-requirement-in-cassandra-tp
I had another question that ties in with my requirement.
How efficient is it to move data from one column family to another column
family ?
Basically, what I want to do is keep track of how "old" a certain data point
is. I have one column family that maintain those data points, and I want to
be a
