[
https://issues.apache.org/jira/browse/YARN-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Li Lu resolved YARN-3914.
-------------------------
Resolution: Won't Fix
Close this issue as discussed before. The community reached an agreement to not
to move forward on this issue. BTW, part of the problems raised in this issue
can be addressed by the entity prefix design proposed in YARN-5715.
> Entity created time should be part of the row key of entity table
> -----------------------------------------------------------------
>
> Key: YARN-3914
> URL: https://issues.apache.org/jira/browse/YARN-3914
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Labels: YARN-5355
>
> Entity created time should be part of the row key of entity table, between
> entity type and entity Id. The reason to have it is to index the entities.
> Though we cannot index the entities for all kinds of information, indexing
> them according to the created time is very necessary. Without it, every query
> for the latest entities that belong to an application and a type will scan
> through all the entities that belong to them. For example, if we want to list
> the 100 latest started containers in an YARN app.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
