[DOCS-10322] Clarify eligibility of compound indexes that contain geospatial and text indexes Created: 26/May/17  Updated: 30/Oct/23  Resolved: 10/Feb/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Critical - P2
Reporter: Chris Harris Assignee: Dave Cuthbert (Inactive)
Resolution: Fixed Votes: 5
Labels: ready-for-work, reopened
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-37059 Prefix of compound text indexes canno... Closed
Participants:
Days since reply: 1 year, 14 weeks, 6 days ago
Epic Link: DOCSP-26173

 Description   

Our documentation for Sparse Indexes contains the following:

sparse Index and Incomplete Results

If a sparse index would result in an incomplete result set for queries and sort operations, MongoDB will not use that index unless a hint() explicitly specifies the index.

Geospatial and text indexes are sparse by definition and are documented as such (eg: here). While it can be concluded from that documentation that there are associated eligibility considerations, it is not nearly as clear as what is described in the Sparse Index documentation above.

This can be problematic since these indexes can also be compound. In multiple places in the documentation we highlight the benefits of constructing indexes in such a way that their prefix ordering supports multiple query shapes (eg here and here. The sparse nature of these indexes adds additional constraints when designing them. The documentation should more clearly highlight these considerations.



 Comments   
Comment by Emet Ozar [ 27/Oct/22 ]

christopher.harris@mongodb.com Hey Christopher, just wanted to check in to see if this ticket is still relevant? Thank you, Emet CC: sarah.olson@mongodb.com ashley.brown@mongodb.com 

Generated at Thu Feb 08 08:00:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.