[
https://issues.apache.org/jira/browse/CASSANDRA-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828210#comment-13828210
]
Alex Liu commented on CASSANDRA-6311:
-------------------------------------
Add cassandra.input.native.enable setting to Hadoop configuration. If it's set
to true, use new CqlRecordReader, otherwise use the old CqlPagingRecordReader.
Add cassandra.input.cql setting to Hadoop configuration. We can specify the
complete Cql query. If it's set(Don't need set KS/CF/Columns/WhereClauses), we
parse the cql query to get the keyspace/column family/where clauses. Modify
the input cql query to add partition keys and cluster columns to the select
clauses if they are not included, add token(key...) range clauses to the where
clauses. If it's not set, we use the old way of passing
KS/CF/Columns/WhereClauses.
Once we completely transit to new CqlRecordReader, we can delete
CqlPagingRecordReader and CqlPagingInputFormat classes. Instead we use
CqlInputFormat. Remove cassandra.input.native.enable,
cassandra.input.where.clause and cassandra.input.columnfamily.columns settings
> 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)
