[DOCS-3081] Conflicting documentation on eval nolock option Created: 07/Apr/14 Updated: 24/Jul/14 Resolved: 24/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | David Hows | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint-rollover | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 29 weeks, 6 days ago |
| Description |
|
Taken from FAQ: Concurrency Taken from eval These two doc's pages conflict each other regarding writes performed when the nolock option is specified. Can we please fix this up and ideally clarify the use-cases for using the lock vs nolock as this will help end-users understand the what/why of supplying the nolock option. |
| Comments |
| Comment by Githook User [ 24/Jul/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: manually apply |
| Comment by Githook User [ 24/Jul/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |