You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Vrushali C (JIRA)" <ji...@apache.org> on 2017/06/23 01:08:00 UTC
[jira] [Created] (YARN-6734) Ensure sub-application user is
extracted & sent to timeline service
Vrushali C created YARN-6734:
--------------------------------
Summary: Ensure sub-application user is extracted & sent to timeline service
Key: YARN-6734
URL: https://issues.apache.org/jira/browse/YARN-6734
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Vrushali C
After a discussion with Tez folks, we have been thinking over introducing a table to store sub-application information. YARN-6733
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.
YARN-6733 tracks the code changes needed for table schema creation.
This jira tracks writing to that table, updating the user name fields to include sub-application user etc. This would mean adding a field to Flow Context which can store an additional user
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org