[YARN-6734] Ensure sub-application user is extracted & sent to timeline service

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, YARN-5355, 3.0.0-beta1, YARN-5355-branch-2
• Component/s: timelineserver
• Labels: atsv2-subapp
• Hadoop Flags: Reviewed
• Assignee: Rohith Sharma K S
• Reporter: Vrushali C
• Created: 23/Jun/17 01:07
• Updated: 21/Oct/17 06:05
• Resolved: 28/Jul/17 18:10

Description

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

Issue Links

• is depended upon by: YARN-6861 Reader API for sub application entities