[
https://issues.apache.org/jira/browse/CASSANDRA-8576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492934#comment-14492934
]
Piotr Kołaczkowski commented on CASSANDRA-8576:
-----------------------------------------------
{noformat}
pig.registerQuery("composite_rows = LOAD 'cql://cql3ks/compositekeytable?" +
defaultParameters + nativeParameters +
"&where_clause=key1%20%3D%20%27key1%27%20and%20key2%20%3D%20111%20and%20column1%3D100&page_size=2'
USING CqlNativeStorage();");
{noformat}
Things like this make my eyes cry. I know, this already was like this, but why
can't we just specify the query in a human readable form and call a function to
url encode it?
> Primary Key Pushdown For Hadoop
> -------------------------------
>
> Key: CASSANDRA-8576
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8576
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Reporter: Russell Alexander Spitzer
> Assignee: Alex Liu
> Fix For: 2.1.5
>
> Attachments: 8576-2.1-branch.txt, 8576-trunk.txt
>
>
> I've heard reports from several users that they would like to have predicate
> pushdown functionality for hadoop (Hive in particular) based services.
> Example usecase
> Table with wide partitions, one per customer
> Application team has HQL they would like to run on a single customer
> Currently time to complete scales with number of customers since Input Format
> can't pushdown primary key predicate
> Current implementation requires a full table scan (since it can't recognize
> that a single partition was specified)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
