[
https://issues.apache.org/jira/browse/CASSANDRA-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055721#comment-13055721
]
Jim Ancona commented on CASSANDRA-2773:
---------------------------------------
I applied the 0.8 patch and added a couple of tests to ColumnFamilyStoreTest.
The tests trigger the UnsupportedOperationException in 0.7.6 and return the
correct values with the patch applied. Would you like me to test the same
scenario against an actual patched server?
> "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: Critical
> Fix For: 0.8.2
>
> Attachments: 2773-v2.txt, 2773.txt, cassandra.log,
> v1-0001-allow-deleting-a-rowand-updating-indexed-columns-init-.txt,
> v1-0002-CASSANDRA-2773-Add-unit-tests-to-verfy-fix-cherry-pick.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
