cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4466) ColumnFamilyRecordReader hadoop integration fails with ghost keys
Date Fri, 27 Jul 2012 19:23:35 GMT


Jonathan Ellis commented on CASSANDRA-4466:

setting rows=null is the signal to stop looping over that inputsplit, so that's not going
to work very well in the general case.
> ColumnFamilyRecordReader hadoop integration fails with ghost keys
> -----------------------------------------------------------------
>                 Key: CASSANDRA-4466
>                 URL:
>             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 #2855 (
), to prevent ghost keys appearing in a hadoop map. 
> The call stack trace is attached.
> I made a one-line change to, 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:!default.jspa
For more information on JIRA, see:


View raw message