It's really not supported in <= 0.7.6; it can cause index corruption IF the row delete timestamp is higher than the column update's.
This is fixed for 0.7.7 in https://issues.apache.org/jira/browse/CASSANDRA-2773 On Thu, Jun 23, 2011 at 12:46 PM, Jim Ancona <j...@anconafamily.com> wrote: > Since upgrading to 0.7.6-2 I'm seeing the following exception in our > server logs: > > ERROR [MutationStage:1184874] 2011-06-22 23:59:43,867 > AbstractCassandraDaemon.java (line 114) Fatal exception in thread > Thread[MutationStage:1184874,5,main] > java.lang.UnsupportedOperationException: Index manager cannot support > deleting and inserting into a row in the same mutation > at org.apache.cassandra.db.Table.ignoreObsoleteMutations(Table.java:431) > at org.apache.cassandra.db.Table.apply(Table.java:387) > at > org.apache.cassandra.db.RowMutationVerbHandler.doVerb(RowMutationVerbHandler.java:75) > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:72) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > > I see that the code that throws this exception was added as part of > the fix for https://issues.apache.org/jira/browse/CASSANDRA-2401 > > We do have clients that do deletes and inserts in the same mutation > (probably unnecessarily), but is this really something that is not > supported? Or is there some other issue behind this? > > Thanks, > > Jim > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
