[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393645#comment-14393645 ]
Sangjin Lee commented on YARN-3391: ----------------------------------- I am fine with tabling this discussion and revisiting it later in the interest of making progress. I just wanted to add my 2 cents that this is something we already see and experience with hRaven so it's not theoretical. That's the context from our side. The way I see it is that apps that do not have the flow name are basically a degenerate case of a single-app flow. This is unrelated to the app-to-flow aggregation. It has to do with the flowRun-to-flow aggregation. And it's something we want the users to do when they can set the flow name. FWIW... > Clearly define flow ID/ flow run / flow version in API and storage > ------------------------------------------------------------------ > > Key: YARN-3391 > URL: https://issues.apache.org/jira/browse/YARN-3391 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Zhijie Shen > Assignee: Zhijie Shen > Attachments: YARN-3391.1.patch > > > To continue the discussion in YARN-3040, let's figure out the best way to > describe the flow. > Some key issues that we need to conclude on: > - How do we include the flow version in the context so that it gets passed > into the collector and to the storage eventually? > - Flow run id should be a number as opposed to a generic string? > - Default behavior for the flow run id if it is missing (i.e. client did not > set it) > - How do we handle flow attributes in case of nested levels of flows? -- This message was sent by Atlassian JIRA (v6.3.4#6332)