[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085243#comment-16085243 ]
Rohith Sharma K S commented on YARN-6733: ----------------------------------------- bq. cluster ! sub app user ! queryA ! DAG ! 1234 ! queryA_1450024426 Hence the sub app name and entity id. What do you think? The purpose why I was asking to drop is , Firstly, how does subAppName is passed to collector? Secondly, If queries are standard defined then I agree we do need subAppName like TPCH queries. But for adhoc queries, adding whole query into row key does not looks good because adhoc query can be in any length. I think we should NOT add subAppName into row key. > 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 > > > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org