Li Lu commented on YARN-3906:

I looked at the dependency relations among our current outgoing patches. The 
online app-level aggregation POC patch (YARN-3816) depends on this patch. 
YARN-3817 further depends on YARN-3816 (aggregation logic) and YARN-3904 

We'd like to push forward our current progress on the aggregation side, so, 
let's merge the current patches in this order: YARN-3906 and YARN-3904 
concurrently, YARN-3816, and then YARN-3817? We can start posting the POC 
patches of YARN-3816 and 3817 immediately after YARN-3906 and YARN-3904 is in. 

> split the application table from the entity table
> -------------------------------------------------
>                 Key: YARN-3906
>                 URL: https://issues.apache.org/jira/browse/YARN-3906
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>         Attachments: YARN-3906-YARN-2928.001.patch, 
> YARN-3906-YARN-2928.002.patch, YARN-3906-YARN-2928.003.patch, 
> YARN-3906-YARN-2928.004.patch, YARN-3906-YARN-2928.005.patch
> Per discussions on YARN-3815, we need to split the application entities from 
> the main entity table into its own table (application).

This message was sent by Atlassian JIRA

Reply via email to