[
https://issues.apache.org/jira/browse/YARN-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424343#comment-16424343
]
Vrushali C commented on YARN-6936:
----------------------------------
Thanks [~haibochen] for checking that entities are posted in one call. And as
you mentioned, we would like to check on the writer side for the entity type.
[~rohithsharma] , looks like the latest patch does not reflect our discussion
from last call. I understand from your last comment, that sub application
entities are user defined entities. So the type could be anything that the user
would like to set it to? If so, we still need a way to distinguish between sub
app entities and other regular entities. I think we would like to keep the API
same as before and differentiate at the writer side based on entity type for
sub app entities. Do you think we can do something for that...
> [Atsv2] Retrospect storing entities into sub application table from client
> perspective
> --------------------------------------------------------------------------------------
>
> Key: YARN-6936
> URL: https://issues.apache.org/jira/browse/YARN-6936
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Priority: Major
> Attachments: YARN-6936.000.patch, YARN-6936.001.patch,
> YARN-6936.002.patch
>
>
> Currently YARN-6734 stores entities into sub application table only if doAs
> user and submitted users are different. This holds good for Tez kind of use
> cases. But AM runs as same as submitted user like MR also need to store
> entities in sub application table so that it could read entities without
> application id.
> This would be a point of concern later stages when ATSv2 is deployed into
> production. This JIRA is to retrospect decision of storing entities into sub
> application table based on client side configuration driven rather than user
> driven.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
