Use IDL enumerations to decode command type in oplog entries

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • Fully Compatible
    • QO 2024-03-18, QO 2024-04-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the oplog parsing is largely done by IDL, but parsing command names to command enum values is done outside. By moving it into the IDL we make things simpler (especially when adding new command values) and take advantage of IDL performance improvements.

              Assignee:
              Ben Shteinfeld
              Reporter:
              Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: