Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 13 Feb 2012 16:37:00 +0000 (UTC)
From: "Brandon Williams (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <452044566.32084.1329151020123.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <967297363.979.1328508965499.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3859) Add Progress Reporting to
 Cassandra OutputFormats
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-3859:
---------------------------------------------

Samarth, how is this patching working for you?
                
> Add Progress Reporting to Cassandra OutputFormats
> -------------------------------------------------
>
>                 Key: CASSANDRA-3859
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3859
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Hadoop, Tools
>    Affects Versions: 1.1.0
>            Reporter: Samarth Gahire
>            Assignee: Brandon Williams
>            Priority: Minor
>              Labels: bulkloader, hadoop, mapreduce, sstableloader
>             Fix For: 1.1.0
>
>         Attachments: 0001-add-progress-reporting-to-BOF.txt, 0002-Add-progress-to-CFOF.txt
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> When we are using the BulkOutputFormat to load the data to cassandra. We should use the progress reporting to Hadoop Job within Sstable loader because while loading the data for particular task if streaming is taking more time and progress is not reported to Job it may kill the task with timeout exception. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira