Setting locally timeseriesBucketsMayHaveMixedSchemaData during MultiIndexBlock::commit might generate catalog inconsistencies

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 7.3.4, 7.0.13, 6.0.17, 8.0.0-rc16
    • Affects Version/s: 6.0.16, 7.3.3, 7.0.12, 8.0.0-rc15
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v8.0, v7.3, v7.0, v6.0
    • Execution Team 2024-08-05
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With the changes committed under SERVER-91195, we're expecting users to be able to remediate SERVER-91194 by calling collMod with the timeseriesBucketsMayHaveMixedSchemaData option set. This will ensure cluster-wide consistency of the timeseriesBucketsMayHaveMixedSchemaData time-series collection option.

      In order to ensure that cluster-wide consistency is respected, such parameter must never be changed only at replica set level (shard level). There is one code snippet violating this condition during index build: when it is locally detected that there are no mixed schema buckets, the flag is locally unset. This can generate mismatch among different shards and can affect query planning, potentially leading to query incorrectness.

              Assignee:
              Henrik Edin
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: