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

Generalize structure of metadata inconsistency reply

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17

    Description

      Currently the format of each metadata inconsistency object is the following:

      {
         "type":"TYPE",
         "description":"DESC",
         "shard":"SHARD",
         "ns":"NSS",
         "info":{
            "..."
         }
      }
      

      In particular the shard and the namespace field are mandatory for all inconsistencies types.
      To make the format more generic and extensible we should instead adopt the following:

      {
         "type":"TYPE",
         "description":"DESC",
         "details":{
            "shard":"SHARD",
            "namespace":"NSS",
            ...
         }
      }
      

      In this format the only required field are type and description, everything else is optional and should go into the details section.

      Additionally as part of this ticket we should create a static map of TYPE->DESCRIPTION that can be used implicitly when creating new inconsistency object.

      Attachments

        Activity

          People

            pol.pinol@mongodb.com Pol Pinol
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: