[
https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082202#comment-16082202
]
Rohith Sharma K S commented on YARN-6733:
-----------------------------------------
thanks Vrushali for the v0 patch.
I vaguely remember some of the discussion points
# the schema we planned to have
*clusterId!subAppUserName!entityType!entityPrefix!entityId!(applicationUserName)*.
I do not remember why subAppName was added!!? Can you remind me? The last key
combination i.e applicationUserName was in discussion. cc:/[~jrottinghuis]
# For column family, it will be same as entity table but adding more columns
such as applicationName, flowname and flowrunId. This is to do reverse
indexing.
Use case which targeted was
# For given subAppuser,
# # retrieve all the entity-types. /user/$userName/entity-types
# # retriever all the entities for give /user/$userName/entities/$entityType
# # particular entity give user know entity-id.
/user/$userName/entities/$entityType/$entity-id
> 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: 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: [email protected]
For additional commands, e-mail: [email protected]
