Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-17607

Global LOOP graph with conditionals can hit initialization problems


    • Type: Bug
    • Status: Resolved
    • Priority: Not specified
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.4.0
    • Component/s: Thor
    • Labels:


      This was though previously fixed by HPCC-17555.
      The fix there was to ensure that all activities in a global loop graph serialized their initialization information.

      The issue that prompted the fix was an issue involving splitter, which needed to be initialized to know the connected count.

      However, serializing all global loop graph activities was not a good fix, a) because all activities may never be used and b) not all master activities were initialized (not needed to be), which meant the serialized information may be incomplete.

      A better fix would be, as before, to only init/serialize activities that were active (dependent on conditionals) in this execution and tackle the splitter problem in an alternative way.

      The splitter problem needed the total connected count which was initialized in the splitter's init method, if the splitter was never used (due to conditionals) it still needs to ensure that the stop()'s are chained, which previously relied on the # of stops equalling the # of connected outputs.

      Instead of relying on the connected count being initialized, detect the fact it isn't in stop and stop the input immediately on 1st chained stop().


          Issue Links



              • Assignee:
                jakesmith Jake Smith
                jakesmith Jake Smith
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: