[DOCS-10021] Docs for SERVER-27771: Add readConcern::readAfterClusterTime Created: 22/Mar/17 Updated: 17/Nov/17 Resolved: 08/Nov/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-3.6, 3.5.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 14 weeks ago | ||||||||
| Epic Link: | DOCS: 3.6 Server | ||||||||
| Description |
Documentation Request Summary:According to https://jira.mongodb.org/browse/PM-221. Engineering Ticket Description:1. The BSON argument type of the readConcern::readAfterClusterTime will be a Timestamp, but internally it will be converted and used as LogicalTime. The command reply returns the operationTIme also in the Timestamp format. 2. Add support for optional LogicalTime _clusterTime member to ReadConcernArgs.
3. in initialize() Add a restriction that afterClusterTime is only supported for level::majority 4. Add ReplicationCoordinatorImpl::waitUntilClusterTime - it may result in refactoring the ReplicationCoordinatorImpl::waitUntilOptimeForRead to factor out the common part 5. Modify waitForClusterTime() to support the afterClusterTime
6. Unit tests related to readConcernArgs parsing 7. Unit tests for waiting |
| Comments |
| Comment by Githook User [ 08/Nov/17 ] |
|
Author: {'name': 'kay', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}Message: |