Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-10308

Component id assignement is not consistent across PipelineContext instances

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • P1
    • Resolution: Fixed
    • None
    • 2.24.0
    • cross-language, sdk-py-core
    • None

    Description

      The "unique ref" ids used in PipelineContext are generated on the fly, which can cause us to get a different id for the same component in different contexts.

      This becomes a problem when ExternalTransform is used, because it creates its own pipeline context for expansion. So its possible the component ids in the expansion request will actually refer to an entirely different component when the pipeline is finally assembled for execution.

      Attachments

        Issue Links

          Activity

            People

              bhulette Brian Hulette
              bhulette Brian Hulette
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 6.5h
                  6.5h