[
https://issues.apache.org/jira/browse/TEZ-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639889#comment-14639889
]
Hitesh Shah commented on TEZ-2627:
----------------------------------
A simpler approach to the isSet() question would be just to use the
Configuration::get(String propertyName) API to check whether an entry exists or
not and then invoke getInt and setPriority only if the value is non-null. This
does mean that the new api in AMConfiguration is no longer needed.
> Support for Tez Job Priorities
> ------------------------------
>
> Key: TEZ-2627
> URL: https://issues.apache.org/jira/browse/TEZ-2627
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Saikat
> Assignee: Saikat
> Attachments: TEZ-2627.1.patch, TEZ-2627.2.patch, TEZ-2627.patch
>
>
> When a Tez Job is submitted via TezClient, an ApplicationSubmissionContext is
> created before submitting the job. ApplicationSubmissionContext has a
> priority field which can be used to provide a priority for the job.
> There is an ongoing effort in the Yarn Community to enable application
> priorities(https://issues.apache.org/jira/browse/YARN-1963).
> https://issues.apache.org/jira/browse/YARN-2003 implements the necessary
> changes in RM and Capacity Scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
