[DOCS-8502] ReadConcern docs should include canonical sample usage Created: 04/Aug/16 Updated: 26/Jul/18 Resolved: 05/Apr/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | post-launch_mongodb-3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Achille Brighton | Assignee: | Kay Kim (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 45 weeks ago |
| Description |
|
With the recent introduction of readConcern, there have been many questions on why it's useful and purpose it serves (i.e: avoiding reading writes which may potentially roll back). Docs should perhaps publish some canonical examples for a simple schema along with details for how readConcern should be used in conjunction with writeConcern. |
| Comments |
| Comment by Kay Kim (Inactive) [ 05/Apr/18 ] |
|
In the middle of rewrite for read concern. |