Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 4 Dec 2013 23:19:39 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12504901.1303401483184.73833.1386199178995@arcas>
In-Reply-To: <JIRA.12504901.1303401483184@arcas>
References: <JIRA.12504901.1303401483184@arcas>
Subject: [jira] [Commented] (CASSANDRA-2527) Add ability to snapshot data as
 input to hadoop jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839472#comment-13839472 ] 

Jonathan Ellis commented on CASSANDRA-2527:
-------------------------------------------

bq. Not really feasible; Hadoop is a special case since we can seq scan sstables without having to fully "open" them (sample indexes, populate key cache, etc)

... so, I'm not sure how interesting that leaves this given that we're trying to do predicate pushdown for Hadoop queries that could be indexed, for instance.

> Add ability to snapshot data as input to hadoop jobs
> ----------------------------------------------------
>
>                 Key: CASSANDRA-2527
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2527
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jeremy Hanna
>            Assignee: Tyler Hobbs
>            Priority: Minor
>              Labels: hadoop
>             Fix For: 2.1
>
>
> It is desirable to have immutable inputs to hadoop jobs for the duration of the job.  That way re-execution of individual tasks do not alter the output.  One way to accomplish this would be to snapshot the data that is used as input to a job.


--
This message was sent by Atlassian JIRA
(v6.1#6144)