[
https://issues.apache.org/jira/browse/CASSANDRA-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946799#comment-13946799
]
Piotr Kołaczkowski edited comment on CASSANDRA-6311 at 3/25/14 5:07 PM:
------------------------------------------------------------------------
But wouldn't a wrapper class impact performance of the new Hadoop API? This
looks like adding another layer of indirection and those wrappers need to be
created so they add GC pressure.
If I had to chose between a wrapper and reflection hack, I'd go with reflection
hack because, as ugly as it is, it affects only the old API.
was (Author: pkolaczk):
But wouldn't a wrapper class impact performance of the new Hadoop API? This
looks like adding another layer of indirection and those wrappers need to be
created so they add GC pressure.
> 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-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)
