Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-86085

Improve naming/semantics around frozen time-series buckets and reopening

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2024-03-18

      The timeseries::bucket_catalog::conflictsWithReopening function does not return true for frozen buckets even though logically they do conflict with reopening. The reason that it doesn't return true in this case is because its callers often use it to determine whether to return a write conflict, but a write conflict is not the correct action for a frozen bucket because its state will never change. We may want to adjust the naming/function usage here in order to improve the semantics.

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: