[SERVER-81222] Separate time-series arbitrary updates in concurrency sharding test Created: 19/Sep/23 Updated: 29/Oct/23 Resolved: 21/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Yuhong Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution NAMR Team 2023-10-02 | ||||
| Participants: | |||||
| Linked BF Score: | 68 | ||||
| Description |
|
We added the new test case to the workload originally only supporting meta-only updates and tried to check if the feature flag is enabled dynamically. But the check does not really work in a sharded cluster as it could have shards with different versions. We can separate the new test into its own file with the feature flag tag to keep the testing coverage and make multiversion tests happy. |
| Comments |
| Comment by Githook User [ 20/Sep/23 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: |