Zhijie Shen commented on YARN-3049:

[~sjlee0], yeah, I agree it's not a decent solution to let the user code to 
trigger writing the app to flow mapping. The reason why I did this before is 
that we can avoid check and put for each individual entity put request, which 
will obviously slow dow the write path.  Detecting the application created 
event sounds a reasonable option.  However, I'm afraid we cannot hide it inside 
the writer as the implementation detail, because the writer is bind to the 
session of an application. One solution I can think of is tackling the session 
start in the app collector. Upon the first put request received by the app 
collector, we tell the writer to also write the app to flow mapping. What do 
you think?

> [Storage Implementation] Implement storage reader interface to fetch raw data 
> from HBase backend
> ------------------------------------------------------------------------------------------------
>                 Key: YARN-3049
>                 URL: https://issues.apache.org/jira/browse/YARN-3049
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Zhijie Shen
>         Attachments: YARN-3049-WIP.1.patch, YARN-3049-WIP.2.patch, 
> YARN-3049-WIP.3.patch, YARN-3049-YARN-2928.2.patch, 
> YARN-3049-YARN-2928.3.patch
> Implement existing ATS queries with the new ATS reader design.

This message was sent by Atlassian JIRA

Reply via email to