[SERVER-33114] Unpack applyOps oplog entries in change streams and generate a notification for each individual write Created: 03/Feb/18 Updated: 29/Oct/23 Resolved: 13/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Ian Boros |
| 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: | Query 2018-04-09, Query 2018-04-23 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Githook User [ 13/Apr/18 ] |
|
Author: {'email': 'ian.boros@10gen.com', 'name': 'Ian Boros'}Message: |
| Comment by Ian Boros [ 13/Apr/18 ] |
|
Re-opening, as the follow-up patch which allows this to work under whole-cluster change streams has yet to be pushed. |
| Comment by Githook User [ 12/Apr/18 ] |
|
Author: {'email': 'ian.boros@10gen.com', 'name': 'Ian Boros'}Message: |
| Comment by Spencer Brody (Inactive) [ 23/Mar/18 ] |
|
Tricky part will be making sure it's possible to resume mid-way through a single applyOps. Just using the documentKey likely isn't sufficient as the same document might be modified multiple times in the same transaction. This will likely require a format change to the resumeToken. |
| Comment by Spencer Brody (Inactive) [ 22/Mar/18 ] |
|
We should include the lsid and txnNumber in each notification from a write that was part of a transaction. |