[SERVER-48452] Internal readers should default to reading without a timestamp Created: 27/May/20 Updated: 29/Oct/23 Resolved: 10/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 4.4.0 |
| Fix Version/s: | 4.8.0, 4.4.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Backport Requested: |
v4.7, v4.4
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2020-09-07, Execution Team 2020-09-21 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Internal readers should default to using the kNoTimestamp ReadSource. Users of AutoGetCollectionForRead are subject to having their ReadSource changed, which is not always desirable and leads to unexpected behavior. Since internal readers have a "local" readConcern by default, despite not originating from a command, they are still eligible for changing their ReadSource. Only reads originating from commands should change their ReadSource. |
| Comments |
| Comment by Githook User [ 15/Sep/20 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: Removes ReadSource::kUnset in favor of kNoTimestamp as the default Makes the following behavioral changes to AutoGetCollectionForRead:
(cherry picked from commit 11c68393df88a6f1ea4855e6ac15e54ca9f9d976) |
| Comment by Githook User [ 10/Sep/20 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: Removes ReadSource::kUnset in favor of kNoTimestamp as the default Makes the following behavioral changes to AutoGetCollectionForRead:
|