[SERVER-49682] Update Idempotency tests should not ignore field ordering Created: 17/Jul/20 Updated: 03/Sep/20 Resolved: 03/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Arun Banala |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Query 2020-09-21 | ||||||||
| Participants: | |||||||||
| Description |
|
This is subject to, if we move $v:1 oplog entries to $v:2 oplog entires. Once we move $v:1 updates to $v:2 we can change the Idempotency tests consider field ordering |
| Comments |
| Comment by Arun Banala [ 03/Sep/20 ] |
|
The Idempotency tests already validate the field order for $v:2 updates. The $v:1 updates cannot guarantee field order. Once we move all the $v:1 updates to $v:2 this problem should go away. |