[DOCS-5964] Document removal of support for "cursorInfo" command Created: 03/Aug/15 Updated: 11/Jan/17 Resolved: 11/Dec/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Qingyang Chen | Assignee: | Andrew Aldridge |
| Resolution: | Done | Votes: | 0 |
| Labels: | docs-3.2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Days since reply: | 8 years, 9 weeks, 2 days ago | ||||||||||||||||||||||||
| Description |
|
The "cursorInfo" command has been replaced by the "serverStatus.metrics.cursor" serverStatus section, and has been documented as deprecated since 2.6.0. Now the command has been completely removed for 3.2. Also, the "db.serverStatus().cursors" section has been removed as well. |
| Comments |
| Comment by Githook User [ 14/Dec/15 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |