Timeseries reopen verification function does not properly handle meta in different order

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • v8.1, v8.0
    • Storage Execution 2025-07-21
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When nested metadata is used with a driver/application that can send elements in random order the verification function will fail, preventing bucket reopening from succeeding. The inserts will retry in a new bucket, but this can lead to very poor bucketing as it essentially disables any form of bucket reopening.

            Assignee:
            Binh Vo
            Reporter:
            Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: