[SERVER-74562] always set fromMigrate in OpObserverImpl::onCreateIndexes and onCreateCollection Created: 02/Mar/23 Updated: 29/Oct/23 Resolved: 08/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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 Team 2023-03-20 | ||||||||
| Participants: | |||||||||
| Description |
|
logMutableOplogEntry current ignores fromMigrate for createIndexes and createCollection operations that are in a multi-document transaction. This is slightly inconsistent with the fromMigrate treatment in some other OpObserver methods such as onDelete. This change is effectively a no-op for the multi-document transaction case because we don't current use these operations for chunk migration in transactions. |
| Comments |
| Comment by Githook User [ 03/Mar/23 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: This change is effectively a no-op for the multi-document transaction case because we |