[jira] [Commented] (CASSANDRA-2773) after restart cassandra, seeing "Index manager cannot support deleting and inserting into a row in the same mutation".

["Boris Yen (JIRA)" <ji...@apache.org>]

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

Boris Yen commented on CASSANDRA-2773:
--------------------------------------

sure, I know what you mean.

however, when the user uses it the wrong way, the server should at least response an error or exception... not just hold the connection and do nothing...

In addition, the server should not be dead forever, when this kind of exception occurs. 

> after restart cassandra, seeing "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.8.0
>            Reporter: Boris Yen
>
> 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