[jira] Updated: (CASSANDRA-21) get_columns_in fails when when routed to a node that isn't the home for the key

["Sandeep Tata (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandeep Tata updated CASSANDRA-21:
----------------------------------

    Attachment: patch_readmessage.txt
                ReadMessageTest.java

ReadMessageTest simple constructs a readmessage, serializes it, deserializes it and checks if this was the same as the original.

My patch fixes it for the case of get_columns_in breaking. Haven't tested other cases.

> get_columns_in fails when when routed to a node that isn't the home for the key
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: all
>            Reporter: Sandeep Tata
>         Attachments: patch_readmessage.txt, ReadMessageTest.java
>
>
> get_columns_in fails when the request cannot be satisfied locally.
> What steps will reproduce the problem?
> 1. Insert multiple columns in some row R in a Cassandra cluster that 
> contains more than 1 node.
> 2. Submit a get_columns_in query to a bunch of nodes. Using the python thrift 
> interface, this is something  like: 
> ./Cassandra-remote -h node0:9160 get_columns_in 'Mailbox' 'rowid123' 
> 'HeaderList' "['col1','col2']"
> ./Cassandra-remote -h node1:9160 get_columns_in 'Mailbox' 'rowid123' 
> 'HeaderList' "['col1','col2']"
>  
> I've traced the error to a bug in how ReadMessage.java gets de-serialized. See attached unit-test to reproduce this.
> I'm also attaching a patch that fixes this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.