[
https://issues.apache.org/jira/browse/HADOOP-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628520#action_12628520
]
Amir Youssefi commented on HADOOP-3973:
---------------------------------------
When new interface is committed (HADOOP-1230 issue by Owen) this issue is
resolved as well. Meanwhile we have provided workarounds in above discussions.
I'm closing the issue.
Custom MapRunnable can address part A (mapper) but not part B (reducer) in
above comment:
https://issues.apache.org/jira/browse/HADOOP-3973?focusedCommentId=12623810#action_12623810
BTW, Pig's LIMIT (Top) is at it's pick performance when used with this. In
future Pig can break out using coming releases of Hadoop,
> Breaking out of a task
> ----------------------
>
> Key: HADOOP-3973
> URL: https://issues.apache.org/jira/browse/HADOOP-3973
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: Amir Youssefi
>
> Occasionally a mapper/reducer is done without need to see more input data. If
> we provide a way to break out and skip reading the rest of input then job
> finishs earlier and resources are spared.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
