[
https://issues.apache.org/jira/browse/CASSANDRA-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946714#comment-13946714
]
Sylvain Lebresne commented on CASSANDRA-6311:
---------------------------------------------
I don't really understand what's going on here but something is not right so
I've reverted this for now.
bq. Which should be opened up, so the properties can be set.
If you mean that you want the java driver to add some {{setColumnDefintions}}
and {{setData}} to the it's {{Row}} object, then there is no chance of this
happening: that would make sense for the driver from an API point of view,
{{Row}} is very much an immutable object on purpose. That being said, if you
really really want, {{Row}} is actually an interface in the driver, so one can
write some mutable implementation if he really wants to. But I'm a bit
surprised the Hadoop API forces you to go there tbh.
> 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)
