Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-2928 YARN Timeline Service v.2: alpha 1
  3. YARN-3391

Clearly define flow ID/ flow run / flow version in API and storage

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.0, 3.0.0-alpha1
    • Component/s: timelineserver
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      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?

        Attachments

        1. YARN-3391.5.patch
          47 kB
          Zhijie Shen
        2. YARN-3391.4.patch
          47 kB
          Zhijie Shen
        3. YARN-3391.3.patch
          47 kB
          Zhijie Shen
        4. YARN-3391.2.patch
          47 kB
          Zhijie Shen
        5. YARN-3391.1.patch
          47 kB
          Zhijie Shen

          Issue Links

            Activity

              People

              • Assignee:
                zjshen Zhijie Shen
                Reporter:
                zjshen Zhijie Shen
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: