Rely on timeseries::optionsAreEqual when comparing timeseries options in checkMetadataConsistency

XMLWordPrintableJSON

    • Catalog and Routing
    • Fully Compatible
    • v8.0, v7.0
    • CAR Team 2025-07-07
    • 1
    • None
    • 3
    • TBD
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      When checkMetadataConsistency compares timeseries options, it performs a simple BSON comparison that may return false positives when comparing missing fields with fields that are set to their default values (semantically equivalent to an unset field).

      We should rely on timeseries::optionsAreEqual that takes into account the default value for potentially missing fields, such as bucketMaxSpanSeconds.

            Assignee:
            Pierlauro Sciarelli
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: