[ 
https://issues.apache.org/jira/browse/CASSANDRA-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054582#comment-13054582
 ] 

Jonathan Ellis commented on CASSANDRA-2773:
-------------------------------------------

I explained on-list that I'm not comfortable committing this to 0.7.  The 
critical thing we need to deliver in 0.7 at this stage is stability.  

The rarity of the problem combined with the complexity of the code involved 
leads me to conclude that it's better to live with a bug we know how to avoid, 
than risk introducing new ones.  Remember, the risk of new bugs affects 
_everyone_, while the fix can only benefit those who were generating the 
unusual mutation pattern here.  It's our responsibility to take a balanced view.

For the rare people who do find themselves affected here, your options include
- stay on < 0.7.6
- drain the commitlog with an earlier version before upgrading, then re-upgrade 
to 0.7.6 after fixing your code to not generate problematic mutations
- run an unofficial build with this patch included
- upgrade to 0.8.2 when released

> "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
>
>
> 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

        

Reply via email to