Clarify yield behavior in PlanExecutorExpress::readyPlanExecution for write conflict and backoff cases

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      (I created this ticket to satisfy the linter and have a ticket number)

      The readyPlanExecution overloads for WaitingForYield and WaitingForBackoff in plan_executor_express.cpp (lines ~433 and ~451) both call _plan.temporarilyReleaseResourcesAndYield with a no-op lambda after handling write conflict / temporarily-unavailable backoff. It is unclear whether yielding with a no-op is the intended behavior in these cases — confirm or correct it.

            Assignee:
            Unassigned
            Reporter:
            Niels Lohmann
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: