[SERVER-50208] Modify existing update tests to guarantee $v:2 oplog entries generation Created: 10/Aug/20 Updated: 29/Oct/23 Resolved: 02/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Ruoxin Xu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2020-09-07 |
| Participants: |
| Description |
|
After we switch to $v:2 oplog entires as default, we should ensure that we have some tests in core/ and concurrency/ which can generate $v:2 oplog entries. They can be done by adding a large padding fields to the documents in the tests, or by creating new tests. |
| Comments |
| Comment by Githook User [ 02/Sep/20 ] |
|
Author: {'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}Message: |