[
https://issues.apache.org/jira/browse/CASSANDRA-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947415#comment-13947415
]
Dave Brosius commented on CASSANDRA-6311:
-----------------------------------------
+ public boolean next(Long key, Row value) throws IOException
+ {
+ if (nextKeyValue())
+ {
+ ((WrappedRow)value).setRow(getCurrentValue());
+ return true;
+ }
+ return false;
+ }
This assumes the parameter is a certain type not in evidence by the method
signature, which in general is a brittle thing to do.
> 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.7
>
> Attachments: 6311-v10.txt, 6311-v11.txt, 6311-v3-2.0-branch.txt,
> 6311-v4.txt, 6311-v5-2.0-branch.txt, 6311-v6-2.0-branch.txt, 6311-v7.txt,
> 6311-v8.txt, 6311-v9.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.2#6252)
