Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4233

Revisit handling of expr codegen failures

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: Impala 2.8.0
    • Fix Version/s: None
    • Component/s: Backend
    • Labels:

      Description

      FragmentInstanceState::Open() can fail if codegen of expressions fails:

            // It shouldn't be fatal to fail codegen. However, until IMPALA-4233 is fixed,
            // ScalarFnCall has no fall back to interpretation when codegen fails so propagates
            // the error status for now.
            RETURN_IF_ERROR(runtime_state_->CodegenScalarFns());
      

      In principle many functions can be executed without codegen - after IMPALA-4356 was merged, we always initialise the interpreted path, unless the function requires codegen.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kwho Michael Ho
                Reporter:
                bharathv Bharath Vissapragada
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: