[SERVER-75384] Generalize structure of metadata inconsistency reply Created: 28/Mar/23  Updated: 29/Oct/23  Resolved: 05/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17
Participants:

 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.



 Comments   
Comment by Githook User [ 05/Apr/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-75384 Generalize structure of metadata inconsistency reply
Branch: master
https://github.com/mongodb/mongo/commit/8107c85a3d13db50f3bfc9dd2877bcd7552e5635

Generated at Thu Feb 08 06:30:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.