Re: Update vs Delete/Insert

2010-06-16 Thread aaron morton
It may make sense to use a secondary index for the counts. You could store the counts in both places and use a batch mutation to update them. It does not give you a transaction guarantee, but it will mean you still make one request to Cassandra. e.g. { : : } The secondar

RE: Update vs Delete/Insert

2010-06-16 Thread Dr . Martin Grabmüller
Hi Colin, > From: Colin Vipurs [mailto:zodiac...@gmail.com] [...] > I've got some data that I'm doing counts on, stored in a CF as: > > { > : > : > > } [...] > { > : PLACEHOLDER > : PLACEHOLDER > } > > would be a better way of storing the data? Does anyone know t

Update vs Delete/Insert

2010-06-16 Thread Colin Vipurs
I've got some data that I'm doing counts on, stored in a CF as: { : : } With updates happening as an insert on the specific column. I need to extract the top X values by count and I was wondering if storing this as: { : PLACEHOLDER : PLACEHOLDER } would be a bett