[
https://issues.apache.org/jira/browse/CASSANDRA-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213550#comment-13213550
]
Brandon Williams commented on CASSANDRA-3859:
---------------------------------------------
bq. one thing I could think of, is if they are adding a lot of batches, we
don't actually call progress until the loop is over
I'm not sure what you mean, we report the progress inside the loop over
mutations in write()
> 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
