Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-91231

Get rid of md.timeseriesBucketingParametersHaveChanged for avoiding confusion/misuses

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1

      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:
            Unassigned Unassigned
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: