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

Jonathan Ellis commented on CASSANDRA-6311:
-------------------------------------------

We should take advantage of changing the class name to simplifying the API.  
With server-side paging, we should be able to just accept a CQL statement as 
our configuration rather than breaking it out into CF/columns/whereclause.

(Which in turn means we'll want to keep the old CPRR around for a version or 
two for compatibility.

> Update CqlPagingRecordReader to use the latest Cql pagination
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-6311
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6311
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Hadoop
>            Reporter: Alex Liu
>            Assignee: Alex Liu
>             Fix For: 2.0.3
>
>         Attachments: 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)

Reply via email to