hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6734) Ensure sub-application user is extracted & sent to timeline service
Date Wed, 26 Jul 2017 11:34:02 GMT

     [ https://issues.apache.org/jira/browse/YARN-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rohith Sharma K S updated YARN-6734:
    Attachment: YARN-6734-YARN-5355.002.patch

updated the patch fixing some of the review comments. The delta changes are below
# Added a test case to verify data is stored in sub application table. 
# Removed unwanted constructor from SubApplicationRowKeyPrefix
# Fixed java doc error and review comment on if checking for subapp user.
# I have not refactored the code since straight refactoring is not possible for enum classes.
It is required to raise a separate task which takes sufficient effort for it. 

> 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
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-6734-YARN-5355.001.patch, YARN-6734-YARN-5355.002.patch
> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message