[DOCS-5973] Clarity Issue: Covered Queries in Sharded Clusters Created: 04/Aug/15 Updated: 26/Jul/18 Resolved: 17/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | William Cross | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 4 weeks, 1 day ago |
| Description |
|
In the section, "Covered Queries in Sharded Clusters," it says:
I think it could be clearer, here. I would prefer if the version information were made up front, and then the update clarified that this was no longer a limitation:
Probably not a big deal, regardless, as it's not wrong, just a little potentially confusing. |
| Comments |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Kay Kim (Inactive) [ 17/Jan/18 ] |
|
The suggested text is not quite correct in the actual limitation, so I just removed the "Changed in version 3.0" from the second paragraph and prefixed the first paragraph with Starting in MongoDB 3.0, ... |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |