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

Stopping a KeyedJoin inside a child query early can cause spurious results

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.6.18
    • Component/s: Thor
    • Labels:
      None

      Description

      If a keyed join activity is inside a child query and it is stopped early (e.g. because of a downstream choosen), then it is not properly reset.
      In particular complete lookup groups from the previous execution may be left for the next execution.

      Also problems with the limiters remaining disabled after CQ restart.
      If there are relatively small numbers of results as might be expected in a CQ this would probably have gone unnoticed. But if KJ was in a LOOP then this unbound limit (effectively unbound lookahead) could cause memory issues.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: