Retriable updates by collection UUID on viewless timeseries ignore UUID

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Hide

      Run the provided test:

       resmoke.py --jobs 1 --runAllFeatureFlagTests  --repeatTests=1 --suites=replica_sets_jscore_passthrough --additionalFeatureFlags="featureFlagCreateViewlessTimeseriesCollections" timeseries_check_uuid_retriable_updates.js
      Show
      Run the provided test: resmoke.py --jobs 1 --runAllFeatureFlagTests  --repeatTests=1 --suites=replica_sets_jscore_passthrough --additionalFeatureFlags="featureFlagCreateViewlessTimeseriesCollections" timeseries_check_uuid_retriable_updates.js
    • Storage Execution 2025-09-15
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When executing a retriable update on timeseries collection, passing a collection UUID different from the actual UUID of the existing collection should raise a CollectionUUIDMismsatch error. Instead, for viewless timeseries the collection UUID is ignored, and the operation succeeded despite the fact that the UUIDs do not match.

        1. timeseries_check_uuid_retriable_updates.js
          1 kB

            Assignee:
            Damian Wasilewicz
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: