[SERVER-68452] Add a jstest to cover the compatibility between DDL coordinator code and recovery documents across FCV versions Created: 01/Aug/22  Updated: 16/Sep/22  Resolved: 16/Sep/22

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

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Tommaso Tocci
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19
Participants:

 Description   

As part of PM-2933, the team is moving from the DDL shard command classes to the DDL coordinator one the logic to determine whether a user request is targeting an existing timeseries sharded collection.

Such change has effects on the value of the `namespace` field stored in the DDL recovery document as part of the operation identifier, which in case of timeseries collection may contain:

  • FCV 6.1: the value of the view namespace
  • FCV 6.0: the value of the buckets namespace

The server code (thanks to the modifications introduced by SERVER-68384) is expected to correctly handle the recovery of DDL operations under the following scenarios:

  • FCV 6.1 re-executing a DDL request based on a recovery document generated by FCV 6.0 code
  • FCV 6.0 re-executing a DDL request based on a recovery document generated by FCV 6.1 code

but we lack the needed jstest to cover this.



 Comments   
Comment by Paolo Polato [ 16/Sep/22 ]

After committing SERVER-62356, it could be verified that the multiversion suites that already exist in Evergreen already offer the code coverage requested by this ticket (which is going to be closed as "Won't do").

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