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

Investigate whether to sanitize collection options upon creation during moveChunk/movePrimary/resharding

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 7.2.0-rc0
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2023-11-13
    • 2

      SERVER-79496 banned some collection options related with encryption starting from v7.2 while SERVER-72229 added an FCV upgrade step in order to sanitize the catalog on all shards and get rid of such options.

      As a result, it will not be possible to clone collections with such options while running under feature compatibility version v7.0 when using v7.2 binaries (and v8.0 binaries in the near future).

      Purpose of this ticket is to audit all collection cloning procedures in the sharding codebase in order to make sure not to clone the banned collection options by sanitizing them using getSanitizedStorageOptionsForSecondaryReplication.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: