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

Jonathan Ellis updated CASSANDRA-4466:
--------------------------------------

    Description: 
When running hadoop-cassandra jobs with range queries over ghost keys, the 
ColumnFamilyRecordReader throws an exception if the last key in a slice_range 
query is a ghost key. 

This seems to be related to changes made in CASSANDRA-2855 to prevent ghost 
keys appearing in a hadoop map. 

The call stack trace is attached.

I made a one-line change to ColumnFamilyRecordReader.java, which seems to solve 
this issue for us.


  was:
When running hadoop-cassandra jobs with range queries over ghost keys, the 
ColumnFamilyRecordReader throws an exception if the last key in a slice_range 
query is a ghost key. 

This seems to be related to changes made in #2855 ( 
https://issues.apache.org/jira/browse/CASSANDRA-2855 ), to prevent ghost keys 
appearing in a hadoop map. 

The call stack trace is attached.

I made a one-line change to ColumnFamilyRecordReader.java, which seems to solve 
this issue for us.


    
> ColumnFamilyRecordReader hadoop integration fails with ghost keys
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-4466
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4466
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>    Affects Versions: 1.1.2
>            Reporter: Niel Drummond
>            Priority: Minor
>             Fix For: 1.1.4
>
>         Attachments: 4466-stack, 4466-v0.patch
>
>
> When running hadoop-cassandra jobs with range queries over ghost keys, the 
> ColumnFamilyRecordReader throws an exception if the last key in a slice_range 
> query is a ghost key. 
> This seems to be related to changes made in CASSANDRA-2855 to prevent ghost 
> keys appearing in a hadoop map. 
> The call stack trace is attached.
> I made a one-line change to ColumnFamilyRecordReader.java, which seems to 
> solve this issue for us.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to