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?