You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ashish Thusoo (JIRA)" <ji...@apache.org> on 2009/05/20 17:06:45 UTC
[jira] Updated: (HIVE-410) Heartbeating for streaming jobs should
not depend on stdout
[ https://issues.apache.org/jira/browse/HIVE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Thusoo updated HIVE-410:
-------------------------------
Attachment: patch-410.txt
The fix is quite simple. I have not been able to add a test case yet as I need miniMR for that. If this goes in before miniMR stuff, I will add a test case in a separate JIRA.
> Heartbeating for streaming jobs should not depend on stdout
> -----------------------------------------------------------
>
> Key: HIVE-410
> URL: https://issues.apache.org/jira/browse/HIVE-410
> Project: Hadoop Hive
> Issue Type: Bug
> Reporter: Venky Iyer
> Assignee: Ashish Thusoo
> Priority: Blocker
> Attachments: patch-410.txt
>
>
> jobs that require iterative processing may take longer than 10 mins to produce rows. This shouldn't be cause to kill the job. Producing keepalive dummy rows to stdout is bad if the data has to go into a Hive table or other Hive steps.
> If we adopt the solution of using stderr to indicate heartbeats, can that be combined with streaming counters (http://hadoop.apache.org/core/docs/current/streaming.html#How+do+I+update+counters+in+streaming+applications%3F )? Also, will limitations on size of stderr break this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.