[YARN-3391] Clearly define flow ID/ flow run / flow version in API and storage

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-alpha1
• Component/s: timelineserver
• Target Version/s: YARN-2928
• Hadoop Flags: Reviewed
• Assignee: Zhijie Shen
• Reporter: Zhijie Shen
• Created: 23/Mar/15 18:49
• Updated: 25/Oct/19 20:25
• Resolved: 10/Apr/15 00:56

Description

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?

Issue Links

• is related to: YARN-3461 Consolidate flow name/version/run defaults
• relates to: YARN-3040 [Data Model] Make putEntities operation be aware of the app's context
• relates to: YARN-3634 TestMRTimelineEventHandling and TestApplication are broken