[
https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094180#comment-16094180
]
Rohith Sharma K S commented on YARN-6733:
-----------------------------------------
Thanks [~vrushalic] for the patch.. I am +1 for the patch. I have asked
[~varun_saxena] offline to take a look at it. Once he reviews , I will commit
it.
Btw, as discussion made in YARN-4455 regarding timestamp qualifier, I also see
that subapplication table also storing timestamp multiplied by qualifier. Any
comment on this? Or did I miss any concession taken for this?
> Add table for storing sub-application entities
> ----------------------------------------------
>
> Key: YARN-6733
> URL: https://issues.apache.org/jira/browse/YARN-6733
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Vrushali C
> Assignee: Vrushali C
> Attachments: IMG_7040.JPG, YARN-6733-YARN-5355.001.patch,
> YARN-6733-YARN-5355.002.patch, YARN-6733-YARN-5355.003.patch,
> YARN-6733-YARN-5355.004.patch, YARN-6733-YARN-5355.005.patch
>
>
> After a discussion with Tez folks, we have been thinking over introducing a
> table to store sub-application information.
> For example, if a Tez session runs for a certain period as User X and runs a
> few AMs. These AMs accept DAGs from other users. Tez will execute these dags
> with a doAs user. ATSv2 should store this information in a new table perhaps
> called as "sub_application" table.
> This jira tracks the code changes needed for table schema creation.
> I will file other jiras for writing to that table, updating the user name
> fields to include sub-application user etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
