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

KeyedJoin can fail with forceRemote options on (seen in regression suite)

    Details

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

      Description

      With #option('forceRemoteKeyedLoopup', true), keyed join forces requests to go to the remote node, even if the part is local.

      However if the files are off cluster (not on any node), this option continues to use the remote handler with an invalid node number, whereas normally if the part is identified as not being local to the cluster, it is handled by a local handler, i.e. it opens the keyed part directly.

      When the forceRemote options are used and the part is off-cluster, it should also force the handler type to local.

      NB: This issue was noticed when running the regression suite in the cloud with multiple nodes, where the files had been created by hthor.

        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: