[
https://issues.apache.org/jira/browse/MAPREDUCE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1120:
-------------------------------------
Fix Version/s: 0.21.0
Affects Version/s: (was: 0.22.0)
0.21.0
Status: Open (was: Patch Available)
bq. Do we need to maintain compatibility on these static functions, since
they're a public API?
I'd say no. They were added in 0.21, which hasn't been released. It can be
patched in both.
Maintaining the separation between "progress" and "completion" polling
intervals offers very little in functionality. Any objections to collapsing
these tunables into a single set method on the {{Job}} instance?
> JobClient poll intervals should be job configurations, not cluster
> configurations
> ---------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1120
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1120
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: mapreduce-1120.txt
>
>
> Job.waitForCompletion gets the poll interval from the Cluster object's
> configuration rather than its own Job configuration. This is
> counter-intuitive - Chris and I both made this same mistake working on
> MAPREDUCE-64, and Aaron agrees as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
