[DOCS-7643] Comment on: "manual/core/index-compound.txt" Created: 13/Apr/16  Updated: 03/Nov/17  Resolved: 11/Jul/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.org/manual/core/index-compound/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0
Screen Resolution: 1440 x 900
repo: docs
source: core/index-compound


Participants:
Days since reply: 6 years, 31 weeks, 1 day ago

 Description   

you are first using, and then creating the index for the sort order example; you should swap these so you create the index, then use it...



 Comments   
Comment by Kay Kim (Inactive) [ 11/Jul/17 ]

Hi. Thanks for filing this ticket. The gist of the section was intended to be:

1) Let's say your applications perform the queries mentioned.

2) Looking at the queries, you might then create the following index which can support both the queries mentioned.

3) But, note that if you do create such an index, that index cannot support this other kind of query.

So, basically, we're not using the index in the first part, just specifying common queries that might be issued via some sample app. And looking at these common queries, you might then decide to create an index to support those. So, more of an assessment of queries, which would then shape the kind of index you might choose to create.

Hope this helps.

Generated at Thu Feb 08 07:54:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.