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

Treat SOAPCALL specially when optimising

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Not specified
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: eclcc, Thor
    • Labels:
      None

      Description

      We sometimes get issues where SOAP calls are made twice from Thor workunits when the result is used in multiple places so presumably the optimiser has decided it's better to do it twice rather than store the result and use it where needed. When we find these we can work around it with INDEPENDENT but it would be helpful not to have to do this. I suspect it might also happen that a SOAP call is made as part of preparing one side of an IF, which is then discarded because of the condition (though I don't have a definite example of that). Could SOAPCALL be treated differently by the optimiser so these don't happen?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              james.wilson James Wilson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: