Evaluate replacing NO_YIELD with INTERRUPT_ONLY

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • Fully Compatible
    • v7.0, v6.0, v5.0
    • QE 2023-06-26, QE 2023-07-10, QE 2023-07-24, QE 2023-08-07, QE 2023-08-21, QE 2023-09-04, QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The existence of INTERRUPT_ONLY implies that there is a use case for a query not being interruptible, but all of our database operations should be interruptible. The task here is to try to remove NO_YIELD entirely and replace it with INTERRUPT_ONLY or at least understand why we still need NO_YIELD.

              Assignee:
              Rushan Chen
              Reporter:
              Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: