Explore if we need to do anything more to prevent accidental usage of spilldb entities on the main write path.

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Storage Execution 2025-06-23
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Specifically, we want to avoid accidental usage of SpillRecoveryUnit on the main write path, or vice versa - usage of WiredTigerRecoveryUnit on the spilldb write path.

      Is there scope for adding any top level asserts to prevent such accidental usage.

              Assignee:
              Gregory Noma
              Reporter:
              Sandeep Dhoot
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: