There's no problem doing deletions with batch_mutate, but you are probably seeing this:
http://wiki.apache.org/cassandra/FAQ#range_ghosts - Tyler On Wed, Dec 15, 2010 at 4:26 PM, Nick Santini <nick.sant...@kaseya.com>wrote: > since the 0.7beta2 version doesnt support indexes for Super CF or for > columns that you might not now the name yet, im supporting them manually by > adding a row on the same CF where the key is the name of the column plus the > value, and in the columns hold the key to the referenced rows > > this works as in i can actually find my rows using the secondary index rows > > but when i try to delete the original row i want to update my secondary > indexs, so i create a mutation map in the same way i did it when i saved my > information, but this time it only contains deletions for those secondary > indexs rows and only for the column referencing to the row being deleted. > but this doesnt seem to work, it comes back successfully (no erros), but im > still able to find the references to the deleted row in those secondary > indexes > > is there any issue trying to run a batch_mutate with only deletions? > > thanks > > Nicolas Santini > >
