[jira] [Comment Edited] (CASSANDRA-6311) Add CqlRecordReader to take advantage of native CQL pagination

["Alex Liu (JIRA)" <ji...@apache.org>]

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

Alex Liu edited comment on CASSANDRA-6311 at 11/26/13 6:26 PM:
---------------------------------------------------------------

The expected user defined cql input must have the followings
{code}
     1) select clause must include partition key columns (to calculate the progress based on the actual CF row processed)
     2) where clause must include token(partition_key1, ...  ,partition_keyn) > ? and 
         token(partition_key1, ... , partition_keyn) <= ?  (in the right order) 
{code}


was (Author: alexliu68):
The expected user defined cql input must have the followings
{code}
     1) select clause must include partition key columns (to calculate the progress based on the actual CF row processed)
     2) where clause must include token(partition_key1 ... partition_keyn) > ? and 
         token(partition_key1 ... partition_keyn) <= ?  (in the right order) 
{code}

> Add CqlRecordReader to take advantage of native CQL pagination
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-6311
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6311
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Hadoop
>            Reporter: Alex Liu
>            Assignee: Alex Liu
>             Fix For: 2.0.4
>
>         Attachments: 6311-v3-2.0-branch.txt, 6331-2.0-branch.txt, 6331-v2-2.0-branch.txt
>
>
> Since the latest Cql pagination is done and it should be more efficient, so we need update CqlPagingRecordReader to use it instead of the custom thrift paging.



--
This message was sent by Atlassian JIRA
(v6.1#6144)