Bulk insert flush — implement production __wt_bulk_flush() orchestrator

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Btree
    • None
    • Storage Engines, Storage Engines - Transactions
    • 0.001
    • None
    • None

      Production implementation phase T4 (~4 days). Begins after both T2 and T3 are complete.

      Changes:

      • __wt_evict_file(): harden WT_SYNC_BULK_FLUSH case to production quality
      • Production __wt_bulk_flush(): wire T2 (suspend/resume) and T3 (rightmost path rebuild) together
      • _curbulk_insert_row(): threshold triggers production _wt_bulk_flush()

      Test: Python smoke test — single flush end-to-end on row-store, final tree is logically correct

      Depends on: WT-17213 (T2), WT-17214 (T3)
      Next: T5, T6 (can run in parallel)

            Assignee:
            Shoufu Du
            Reporter:
            Shoufu Du
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: