Get rid of md.timeseriesBucketingParametersHaveChanged for avoiding confusion/misuses

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: Catalog
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-03-03, CAR Team 2025-03-17, CAR Team 2025-03-31
    • 0
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Due to the reasons pointed out in SERVER-91193, there may be existing mongodb instances with timeseriesBucketingParametersHaveChanged set to inconsistent values.

      Purpose of this ticket is to unset all existing timeseriesBucketingParametersHaveChanged options (set to boost::none) during server start up or upon setFeatureCompatibilityVersion.

              Assignee:
              Joan Bruguera Micó
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: