Thanks to both of you for these very useful and interesting links/proposals.
Best Regards
Hi
Thanks for the answer, as I read the book on Cassandra, I was not aware at
that time on Composite Key which I recently discovered.
Composite Type's are us
On Mon, Dec 5, 2011 at 3:06 PM, wrote:
> Hi
> Thanks for the answer, as I read the book on Cassandra, I was not aware at
> that time on Composite Key which I recently discovered.
>
*Composite Type's are useful for handling data-versions.
*
* *
> * *You mentioned a TTL and let the database remov
I think most of the book for cassandra are outdated, try to get information
from http://www.datastax.com/docs/1.0/index
As for ttl, you could read
http://www.datastax.com/dev/blog/whats-new-cassandra-07-expiring-columns for
more information.
for composite type, you could read
http://www.slideshar
Hi
Thanks for the answer, as I read the book on Cassandra, I was not aware at
that time on Composite Key which I recently discovered.
You mentioned a TTL and let the database remove the date for me. I never read
about that. Is it possible without an external batch ?
I will try to rephra
Not sure I understand your use case, but I think you could use a composite
column instead of composite key.
For example,
UserID:{
TimeUUID1:CartID1,
TimeUUID2:CartID2,
TimeUUID3:CartID3,
}
This way, you could do a slice query on the time if you do not need all the
carts, and you coul
