[ 
https://issues.apache.org/jira/browse/YARN-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134767#comment-16134767
 ] 

Varun Saxena edited comment on YARN-6861 at 8/21/17 6:44 AM:
-------------------------------------------------------------

bq. AM will start with same user but they publish data with doAs user. The 
whole DAG execution will happens with one doAs user.
Yeah I know doAs user would be used. I meant knowing the app id user would not 
be important in this case as there will be only one record returned per entity 
id.
Anyways as you said FROM_ID would contain the app user id so should be good 
enough to differentiate between records.


was (Author: varun_saxena):
bq. AM will start with same user but they publish data with doAs user. The 
whole DAG execution will happens with one doAs user.
Yeah I know doAs user would be used. I meant knowing the app id user would not 
be that important in this case.
Anyways as you said FROM_ID would contain the app user id so should be good 
enough to differentiate between records.

> Reader API for sub application entities
> ---------------------------------------
>
>                 Key: YARN-6861
>                 URL: https://issues.apache.org/jira/browse/YARN-6861
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>              Labels: atsv2-subapp, yarn-5355-merge-blocker
>         Attachments: YARN-6861-YARN-5355.001.patch, 
> YARN-6861-YARN-5355.002.patch, YARN-6861-YARN-5355.003.patch, 
> YARN-6861-YARN-5355.004.patch, YARN-6861-YARN-5355.005.patch, 
> YARN-6861-YARN-5355.006.patch
>
>
> YARN-6733 and YARN-6734 writes data into sub application table. There should 
> be a way to read those entities.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to