hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6256) Add FROM_ID info key for timeline entities in reader response.
Date Sat, 04 Mar 2017 04:57:46 GMT

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

Rohith Sharma K S commented on YARN-6256:
-----------------------------------------

bq. But if you specify that as the fromId, that entity is returned again in the next call
because the fromId is inclusive, right? Then how does UI deal with that? Does it ask for 51
entities in the next page and drop the first (redundant) one? Am I misunderstanding this?
Is making it precise (e.g. making fromId exclusive) feasible?
As far as I discussed with UI experts earlier, they are fine with displaying one entity of
previous page. And also they use this behavior for identifying last page. It is fixed behavior
in ATS1/1.5 . Since behavior is defined I think it should not be an issue. 

bq. l.257: I thought the check for single entity read was intentional (I guess this was introduced
by YARN-4237). Do we no longer need it?
there is no behavior change here, even I surprised why singleEntityReader check required.!!

> Add FROM_ID info key for timeline entities in reader response. 
> ---------------------------------------------------------------
>
>                 Key: YARN-6256
>                 URL: https://issues.apache.org/jira/browse/YARN-6256
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>              Labels: yarn-5355-merge-blocker
>         Attachments: YARN-6256-YARN-5355.0001.patch, YARN-6256-YARN-5355.0002.patch
>
>
> It is continuation with YARN-6027 to add FROM_ID key in all other timeline entity responses
which includes
> # Flow run entity response. 
> # Application entity response
> # Generic timeline entity response - Here we need to retrospect on idprefix filter which
is now separately provided. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message