[
https://issues.apache.org/jira/browse/CASSANDRA-8576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536484#comment-14536484
]
Jeremiah Jordan commented on CASSANDRA-8576:
--------------------------------------------
Bq. It looks better now, but the mixed-cluster during rolling upgrade issue is
still there. If someone upgrades half of the cluster to the version with this
patch, Hadoop jobs will very likely report errors (not sure how bad that will
be - need to test it).
This is only an issue if the jobs are pulling the C* jar off of the nodes and
the jar isn't part of the job itself? So if this is a problem for someone,
they have a work around.
> 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.x
>
> Attachments: 8576-2.1-branch.txt, 8576-trunk.txt,
> CASSANDRA-8576-v2-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)
