[ https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817454#comment-15817454 ]
Varun Saxena commented on YARN-6027: ------------------------------------ bq. That said, what do we think might break or be a problem if we do end up having >1000 runs in one flow in a day? Over time, we would anyways have thousands of runs for that flow. Nothing breaks from our end. From UI side there was a concern about number of flow runs. Anyways that discussion can be taken up on YARN-4489 If we do aggregate data at flow level, wouldn't it be better to have flow ID before user ID in row key. When I was asking about row key, this was the intention. > 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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org