[SERVER-38539] Remove $_internalLatestOplogTimestamp and mergeByPBRT from change streams in 4.4 Created: 11/Dec/18 Updated: 29/Oct/23 Resolved: 25/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | Assignee: | Bernard Gorman |
| 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 2019-07-01 | ||||||||
| Participants: | |||||||||
| Description |
|
In 4.2, we added a new postBatchResumeToken to each batch returned by a change stream, which superseded the older $_internalLatestOplogTimestamp mechanism used when merging the streams on mongoS. However, we had to retain the latter in 4.2 to facilitate upgrade from and downgrade to 4.0. Now that it is no longer necessary, we should remove all remaining traces of $_internalLatestOplogTimestamp from the codebase. |
| Comments |
| Comment by Githook User [ 25/Jun/19 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: |