[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094183#comment-16094183 ] Vrushali C commented on YARN-6733: ---------------------------------- bq. 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? The sub app table will store metrics just like entity or application table do. No change in behavior intended. Is it that you see this table storing metrics differently in the patch.. > 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: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org