ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication, Replication - Failover and Concerns
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Placeholder ticket for making a TODO

      Background

      As part of SERVER-29729, the afterOpTime readConcern field was removed from the IDL and all internal support for it was removed. The afterOpTime field was the attack surface behind three CVEs.

      Problem

      Several JS tests were updated to accept both ErrorCodes.IDLUnknownField (the new behavior, where afterOpTime is an unknown field) and ErrorCodes.FailedToParse (the last_lts / v9.0 behavior, where afterOpTime is still a known field but rejected when combined with incompatible read concern levels).

      This dual-error-code handling was added so the last_lts burn-in tests (which run current-branch JS against v9.0 binaries) continue to pass. Once v9.0 is no longer a supported last-lts version, this multiversion handling is dead code and should be removed.

      Affected tests

      • jstests/replsets/linearizable_read_concern.js
      • jstests/noPassthrough/read_write_concern/readConcern_snapshot.js
      • jstests/noPassthrough/read_write_concern/readConcern_atClusterTime.js
      • jstests/sharding/read_write_concern_defaults_commands_api.js

      Each of these has a TODO comment referencing this ticket.

      Work to do

      Once the last-lts version advances past v9.0, remove the ErrorCodes.FailedToParse fallback from the assert.commandFailedWithCode calls in the tests above so they only assert ErrorCodes.IDLUnknownField.

            Assignee:
            Unassigned
            Reporter:
            Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: