[SERVER-49820] Allow setting destined recipient in oplog entries Created: 23/Jul/20 Updated: 29/Oct/23 Resolved: 03/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M2, PM-234-T-oplog-fetch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 2020-08-10 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The "reshardDest" field should be added to the DurableReplOperation struct.
And the destined recipient should be added as a parameter to OplogEntry::OplogEntry() and makeOplogEntryDoc(). Consider using boost::optional<ShardId> here and the shard_id type in oplog_entry.idl. |
| Comments |
| Comment by Githook User [ 03/Aug/20 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: |