[ https://issues.apache.org/jira/browse/CASSANDRA-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051871#comment-13051871 ]
Sylvain Lebresne commented on CASSANDRA-2773: --------------------------------------------- Hum, we cannot remove the column from cf in ignoreObsoleteMutations() because cf is the original column family from the row mutation and that's racy with commit log write (à la CASSANDRA-2604). We should clone the column family, but maybe it's simpler to add validation logic after all ? In any case, it could be worth it adding some comment in Table.apply() or Table.ignoreObsoleteMutations(). > "Index manager cannot support deleting and inserting into a row in the same > mutation" > ------------------------------------------------------------------------------------- > > Key: CASSANDRA-2773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2773 > Project: Cassandra > Issue Type: Bug > Affects Versions: 0.7.0 > Reporter: Boris Yen > Assignee: Jonathan Ellis > Priority: Minor > Fix For: 0.8.2 > > Attachments: 2773.txt > > > I use hector 0.8.0-1 and cassandra 0.8. > 1. create mutator by using hector api, > 2. Insert a few columns into the mutator for key "key1", cf "standard". > 3. add a deletion to the mutator to delete the record of "key1", cf > "standard". > 4. repeat 2 and 3 > 5. execute the mutator. > the result: the connection seems to be held by the sever forever, it never > returns. when I tried to restart the cassandra I saw unsupportedexception : > "Index manager cannot support deleting and inserting into a row in the same > mutation". and the cassandra is dead forever, unless I delete the commitlog. > I would expect to get an exception when I execute the mutator, not after I > restart the cassandra. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira