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

make DbCheck be able to create reply message with correct SerializationContext

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Serverless
    • 3

    Description

      When we create a reply message for dbCheck command, we should serialize the nss according to the inputs of command request, eg, the "$tenant" and the "expectPrefix" fields, which comes from unparsed OpMsgRequest and is thread through request's serialization context to the code places where we create the reply message.

      Today, the DbCheck is a BasicCommand which cannot access the unparsed request. We cannot serialize the nss correctly in reply message. 

      In this ticket, we should amke the dbCheck command to be able to create the serialization context when parsing request and use the context when creating reply message.

      Attachments

        Activity

          People

            backlog-server-serverless [DO NOT USE] Backlog - Server Serverless (Inactive)
            sophia.tan@mongodb.com Sophia Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: