Shift DatabaseName parsing from OpMsgRequest to command level

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Shift DatabaseName parsing from OpMsg to command level for the reasons:

      • The OpMsgRequest should not consider the requirements on parsing db of different.
      • Enable the commands to perform enforcement that is more rich than what OpMsgRequest does and custom the db name by themselves, for example, hello/ismaster(SERVER-81553).

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Sophia Tan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: