[SERVER-69664] Investigate the requires_fastcount tests for shard merge protocol Created: 13/Sep/22  Updated: 03/Mar/23  Resolved: 03/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Mathis Bessa Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: shard-merge-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-66147 Passthrough test support for shard me... Closed
Assigned Teams:
Serverless
Participants:

 Description   

For the Shard Merge protocol we currently exclude any test that uses the `requires_fastcount` tag.
Since Tenant Migration is currently running those tests and we will no longer do that for Shard Merge, we will be losing some test coverage.
We should investigate and see if it makes sense to switch from using the fast count to `itcount` or `countDocuments`.
This would result in increasing as much as possible the current test coverage for shard merge.



 Comments   
Comment by Suganthi Mani [ 03/Mar/23 ]

We agreed that shard merge don’t ensure fast count (See the design doc)

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