Varun Saxena commented on YARN-4224:

An important point. For entity table, the row keys are not sorted by created 
time. So when we fetch records from HBase, a limit of 100 for instance does not 
mean that we stop after fetching first 100 records. We will continue fetching 
records till row prefix matches and keep on removing the last entity based on 
created time to limit entities to 100. So, quite a few rows are scanned. If we 
do not make entity type mandatory, this would mean scan of even more rows, 
especially when for generic entity table, entity type can be anything. So I 
would prefer to have a check for entity type being required mandatorily.

> Change the ATSv2 reader side REST interface to conform to current REST APIs' 
> in YARN
> ------------------------------------------------------------------------------------
>                 Key: YARN-4224
>                 URL: https://issues.apache.org/jira/browse/YARN-4224
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>              Labels: yarn-2928-1st-milestone
>         Attachments: YARN-4224-YARN-2928.01.patch, 
> YARN-4224-feature-YARN-2928.wip.02.patch

This message was sent by Atlassian JIRA

Reply via email to