You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/06/29 18:02:05 UTC

[jira] [Updated] (CASSANDRA-8576) Primary Key Pushdown For Hadoop

     [ https://issues.apache.org/jira/browse/CASSANDRA-8576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-8576:
--------------------------------------
    Fix Version/s:     (was: 2.1.x)
                   2.2.x

Let's keep 2.1 for bug fixes and commit this to 2.2.  Can I get a 2.2 patch from Alex?

> 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.2.x
>
>         Attachments: 8576-2.1-branch.txt, 8576-trunk.txt, CASSANDRA-8576-v2-2.1-branch.txt, CASSANDRA-8576-v3-2.1-branch.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)