[
https://issues.apache.org/jira/browse/YARN-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894621#comment-15894621
]
Sangjin Lee edited comment on YARN-6256 at 3/3/17 4:01 PM:
-----------------------------------------------------------
Point taken. I know some entity ids and flow name etc. can get quite long, so
it's pretty easy for such a from-id field to be in the hundreds of bytes. But
again, if we return 100 entities, that would add only tens of kB.
If we are going to keep it for all entities, we might as well keep it for
single-entity queries too for consistency.
was (Author: sjlee0):
Point taken. I know some entity ids and flow name etc. can get quite long, so
it's pretty easy for such a from-id field to be in the hundreds of bytes. But
again, if we return 100 entities, that would add only tens of kB.
> 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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
