[SERVER-74186] Support query on non-wildcard prefix fields with compound wildcard indexes Created: 20/Feb/23  Updated: 29/Oct/23  Resolved: 22/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Ruoxin Xu Assignee: Ruoxin Xu
Resolution: Fixed Votes: 0
Labels: M3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-72469 Add integration tests for compound wi... Closed
Backwards Compatibility: Fully Compatible
Sprint: QO 2023-03-06
Participants:

 Description   

A compound wildcard index(CWI), {a: 1, b: 1, "sub.$**": 1, c: 1}, should be able to use on queries on only the non-wildcard prefix of this index, e.g. query: {a: 1, b: 1}.

This requires:

  1. CWI can generate index keys for document w/o any wildcard field, e.g. {a: 1, b: 1}
  2. Wildcard expanding should expand a wildcard index entry to an IndexEntry even though no wildcard field is in the query.
  3. Fields after such wildcard field should not support non-blocking sort. (In the example above, field 'c' cannot support non-blocking sort)


 Comments   
Comment by Githook User [ 22/Feb/23 ]

Author:

{'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}

Message: SERVER-74186 Support query on non-wildcard prefix fields with compound wildcard indexes
Branch: master
https://github.com/mongodb/mongo/commit/e108de9b68382155d3db7a5a64aeebe641c0e15f

Generated at Thu Feb 08 06:26:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.