[SERVER-74384] Run existing shard merge tests with multitenancySupport enabled. Created: 27/Feb/23 Updated: 07/Mar/23 Resolved: 07/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Didier Nadeau |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Participants: |
| Comments |
| Comment by Suganthi Mani [ 07/Mar/23 ] |
|
Spoke with janna.golden@mongodb.com, agreed to write the targeted tests to test shard merge code with gMultitenancySupport server parameter enabled. Technically, shard merge doesn't depend on how the tenantId is been communicated to Server. It depends on how the tenantId is parsed and stored in DatabaseName object. So, writing targeted tests seems sufficient to build confidence. |