Have an explicit API to skip cache eviction instead of using setCacheMaxWaitTimeout(Milliseconds(1))

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Server Integration
    • Fully Compatible
    • Omnomlog - 2025-11-11
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Milliseconds(1) is a magic number, and it exposes WT implementation details above the storage engine layer. Still using the setCacheMaxWaitTimeout(Milliseconds(1)) but wrapping that in a function. 

            Assignee:
            Gregory Wlodarek
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: