[
https://issues.apache.org/jira/browse/TEZ-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639911#comment-14639911
]
Saikat commented on TEZ-2627:
-----------------------------
[~hitesh] Thanks for your review comments. I had thought about the null check
approach.
If the get() returns non null, then I would still need to pass a default
invalid value to getInt() to check.
And I need the api getPriority in AMConfiguration since yarnconfig is private
to the class.
So, I had implemented it the way as in patch2, since getInt internally does the
null check.
Can you please comment as to how you are expecting the isset() to look like. I
might be missing a point.
for the second comment, I will make the change for logging priority with appid.
> 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)
