[SERVER-55778] Update C++ tests for ReshardingOplogApplicationRules::applyOperation() to test it directly Created: 05/Apr/21 Updated: 29/Oct/23 Resolved: 06/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2021-04-19 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
The ReshardingOplogApplicationRules class is currently tested in C++ through these tests cases in resharding_oplog_applier_test.cpp. Resharding's oplog application rules behave the same when called from ReshardingOplogApplier::applyUntilCloneFinishedTs() as they do when called from ReshardingOplogApplier::applyUntilDone(). Testing the behavior through ReshardingOplogApplier adds an extra layer of orchestration and complexity for something that has already been split out into its own class. We should instead rewrite these C++ tests to call ReshardingOplogApplicationRules::applyOperation() directly. |
| Comments |
| Comment by Githook User [ 05/Apr/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |