[
https://issues.apache.org/jira/browse/YARN-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15584596#comment-15584596
]
Varun Saxena commented on YARN-5715:
------------------------------------
[~sjlee0]
bq. I think it’s fine either way, although I do think the latter is slightly
more user-friendly. What do others think?
Although our use case will typically be to serve it in descending order, but
what if somebody wants it in ascending order ? So I was leaning towards keeping
it as-is and document the case where we may want to invert it.
bq. It may also mean we need to move the LongConverter class to where
TimelineEntity is so that users can use it.
Well the converter interface currently lies in
hadoop-yarn-server-timelineservice. The question thus is does it belong to
hadoop-yarn-api and should we move it to hadoop-yarn-api just for this ? Can't
we just mention that prefix will be taken as is. And explain how you achieve
descending order by adding it in documentation. We can probably give example of
created time.
Or add another method in TimelineEntity which inverts and sets prefix ID. Its
just one line so duplication of code shouldn't be much of an issue.
Thoughts ?
> introduce entity prefix for return and sort order
> -------------------------------------------------
>
> Key: YARN-5715
> URL: https://issues.apache.org/jira/browse/YARN-5715
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Rohith Sharma K S
> Priority: Critical
> Attachments: YARN-5715-YARN-5355.01.patch,
> YARN-5715-YARN-5355.02.patch, YARN-5715-YARN-5355.03.patch
>
>
> While looking into YARN-5585, we have come across the need to provide a sort
> order different than the current entity id order. The current entity id order
> returns entities strictly in the lexicographical order, and as such it
> returns the earliest entities first. This may not be the most natural return
> order. A more natural return/sort order would be from the most recent
> entities.
> To solve this, we would like to add what we call the "entity prefix" in the
> row key for the entity table. It is a number (long) that can be easily
> provided by the client on write. In the row key, it would be added before the
> entity id itself.
> The entity prefix would be considered mandatory. On all writes (including
> updates) the correct entity prefix should be set by the client so that the
> correct row key is used. The entity prefix needs to be unique only within the
> scope of the application and the entity type.
> For queries that return a list of entities, the prefix values will be
> returned along with the entity id's. Queries that specify the prefix and the
> id should be returned quickly using the row key. If the query omits the
> prefix but specifies the id (query by id), the query may be less efficient.
> This JIRA should add the entity prefix to the entity API and add its handling
> to the schema and the write path. The read path will be addressed in
> YARN-5585.
--
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
