[
https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801147#comment-15801147
]
Varun Saxena commented on YARN-6027:
------------------------------------
Well, we can potentially reuse the ID. However, the query is within the scope
of a cluster and pagination will be within a specific day so first 2 parts are
sort of unnecessary.
Either ways, we may have to consider escaping the delimiters("/") if they are
part of the string itself. Also user will have to be checked for "@". However,
@ is not allowed in Linux usernames.
However, assuming cluster is known both by reader and client and timestamp will
always be a number, both can identify how to parse the ID. But some logic will
have to be added at both ends. We cannot directly replace the delimiters and
construct the row key. This needs to be taken care of.
> Support fromId for flows/flowrun apps
> -------------------------------------
>
> Key: YARN-6027
> URL: https://issues.apache.org/jira/browse/YARN-6027
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Labels: yarn-5355-merge-blocker
>
> In YARN-5585 , fromId is supported for retrieving entities. We need similar
> filter for flows/flowRun apps and flow run and flow as well.
> Along with supporting fromId, this JIRA should also discuss following points
> * Should we throw an exception for entities/entity retrieval if duplicates
> found?
> * TimelieEntity :
> ** Should equals method also check for idPrefix?
> ** Does idPrefix is part of identifiers?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
