Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 Jun 2014 23:12:26 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12502474.1301163619931.41497.1403651546189@arcas>
In-Reply-To: <JIRA.12502474.1301163619931@arcas>
References: <JIRA.12502474.1301163619931@arcas>
Subject: [jira] [Resolved] (CASSANDRA-2391) Create a LoadPushDown
 implementation for CassandraStorage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis resolved CASSANDRA-2391.
---------------------------------------

    Resolution: Later

> Create a LoadPushDown implementation for CassandraStorage
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-2391
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2391
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeremy Hanna
>            Priority: Minor
>              Labels: contrib, hadoop, pig
>
> A LoadPushDown is nice for use with Pig because if you do something like:
> {code}
> rows = LOAD 'cassandra://ks/cf' USING CassandraStorage();
> A = FOREACH rows GENERATE $0;
> {code}
> It would push down the projection and only get the keys from Cassandra instead of all of the rows - it allows Pig to optimize what it gets from Cassandra when it looks at the pig script.  The script above might not be the best example but projections would allow pig to optimize retrieval from Cassandra in something like that.


--
This message was sent by Atlassian JIRA
(v6.2#6252)