[
https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817047#comment-15817047
]
Vrushali C commented on YARN-6027:
----------------------------------
Catching up on this thread.
bq. Sangjin Lee, you remember why the user was kept before flow name in row
key? To achieve user level offline aggregation?
Yes, a flow is identified by the user and cluster it ran on. For instance, I
run a sleep job and you run a sleep job, these are different flows. But if I
run a sleep 10 times in a day, they are all runs of the same flow.
I could not finally decipher in the comments above why there are separate rows
for flow runs of the same flow in the flow activity table? cc [~rohithsharma]?
This should not happen. There should be exactly one row for a flow on a given
day.
Yes, pagination is absolutely to be supported. Also, the UI should limit by
date as well as number of records and return based on whichever limit is hit
first.
We do have a lot of runs of a flow on a given day, for instance hRaven is
running constantly on our cluster. So we do expect several runs of a flow in a
day.
> Support fromId for flows API
> -----------------------------
>
> 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]
