[ 
https://issues.apache.org/jira/browse/YARN-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426097#comment-16426097
 ] 

Haibo Chen commented on YARN-6936:
----------------------------------

The latest patch looks good to me, with two minor comments. 

1) "with in" => "within"

2)
{code:java}
/**
 * <p>
 * Send the information of a number of conceptual entities outside the scope
 * of YARN application to the timeline service v.2 collector. It is a blocking
 * API. The method will not return until all the put entities have been
 * persisted.
 * </p>
 *
 * @param entities the collection of {@link TimelineEntity}
 * @throws IOException if there are I/O errors
 * @throws YarnException if entities are incomplete/invalid
 */
@Public
public abstract void putSubAppEntities(TimelineEntity... entities){code}
Let's be more specific, say 'within the scope of a sub-application' instead of 
'outside the scope of YARN application'. The latter could be User or Queue as 
well.

> [Atsv2] Retrospect storing entities into sub application table from client 
> perspective
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-6936
>                 URL: https://issues.apache.org/jira/browse/YARN-6936
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>            Priority: Major
>         Attachments: YARN-6936.000.patch, YARN-6936.001.patch, 
> YARN-6936.002.patch
>
>
> Currently YARN-6734 stores entities into sub application table only if doAs 
> user and submitted users are different. This holds good for Tez kind of use 
> cases. But AM runs as same as submitted user like MR also need to store 
> entities in sub application table so that it could read entities without 
> application id. 
> This would be a point of concern later stages when ATSv2 is deployed into 
> production. This JIRA is to retrospect decision of storing entities into sub 
> application table based on client side configuration driven rather than user 
> driven. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to