[
https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703109#comment-14703109
]
Sunil G commented on MAPREDUCE-5870:
------------------------------------
bq.As I mentioned above, DEFAULT means there is no explicit priority set, so no
integer priority value should map to the DEFAULT enum
Yes. That's correct, if we set some other value, it will give a wrong meaning
as it can also be a valid priority in real case. I will use plain enum without
any mapping as such.
bq.But at least it keeps the getJobPriority call from crashing
Yes, its like handling a default case. I will try giving a more meaning name
for that ENUM, so users can try new api to get exact integer mapping value for
priority atleast.
As YARN-4014 is getting in, I will handle *mapred* cli command also to set
priority at run time in same ticket.
> Support for passing Job priority through Application Submission Context in
> Mapreduce Side
> -----------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5870
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5870
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-MAPREDUCE-5870.patch, 0002-MAPREDUCE-5870.patch,
> 0003-MAPREDUCE-5870.patch, Yarn-2002.1.patch
>
>
> Job Prioirty can be set from client side as below [Configuration and api].
> a. JobConf.getJobPriority() and
> Job.setPriority(JobPriority priority)
> b. We can also use configuration
> "mapreduce.job.priority".
> Now this Job priority can be passed in Application Submission
> context from Client side.
> Here we can reuse the MRJobConfig.PRIORITY configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
