Understand empty "extractor" configuration strings

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: APIs
    • None
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - 2025-08-29
    • 3
    • v8.2
    • Triage and Release, Technical Services
    • Hide
      Fix for unused config strings that an old backup tool would manually copy over from cluster to cluster. These strings would cause issues under 8.2 despite being empty, because the feature was outright removed. This ticket adds back the ability to accept and ignore an empty config string for these removed features.
      Show
      Fix for unused config strings that an old backup tool would manually copy over from cluster to cluster. These strings would cause issues under 8.2 despite being empty, because the feature was outright removed. This ticket adds back the ability to accept and ignore an empty config string for these removed features.

      Despite MongoDB having never used the extractor config, a case has come up in the wild where it's appeared in a config string, albeit with an empty value.

      This happened because of an historical tool used for backups, which would explicitly set some configuration strings. It would set all strings that could have a persistent value, with an "empty string" fallback. As a result, some clusters that have been migrated from ancient Mongo versions have this key set with an empty value.

      For this ticket, it's sufficient to check that the string is empty, otherwise fail with a reasonably obvious error message.

            Assignee:
            Will Korteland
            Reporter:
            Will Korteland
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: