[JAVA-2233] Support new readConcern level "linearizable" Created: 22/Jun/16 Updated: 27/May/22 Resolved: 21/Jul/16 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Query Operations |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Rathi Gnanasekaran | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | MongoDB 3.4 for Java driver | ||||||||||||
| Server Compat: | 3.4 | ||||||||||||
| Description |
|
A linearizable read avoids returning reads from a "stale" primary (one that has already been superseded by a new primary but doesn't know it yet). It is important to note that readConcern level linearizable does not by itself produce linearizable reads; they must be issued in conjunction with w:majority writes to the same document(s) in order to be linearizable. This feature is exposed as a new value for readConcern.level, "linearizable". |
| Comments |
| Comment by Githook User [ 21/Jul/16 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |
| Comment by Githook User [ 21/Jul/16 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |