[SERVER-23172] Allow use of indices for collation-aware queries that match nested objects or arrays Created: 16/Mar/16  Updated: 06/Nov/17  Resolved: 07/Jul/16

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.3.10

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: David Hatch
Resolution: Done Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Query 16 (06/24/16), Query 17 (07/15/16)
Participants:

 Description   

On our first pass of making index use collation-aware, we disallowed using indices for queries with non-null collators that match nested objects or arrays containing strings. In order to allow index use in this case, we must:
--Update index selection. Currently if a query matches nested objects or arrays, then in order to select an index, the query and the index must both have null collators. We must remove the code that rejects indices in this case.
--Update index key generation. Currently only strings at the top level are transformed into ComparisonKeys. We must also transform strings in nested objects and arrays.
--Update index bounds building. Similarly to index key generation, we must transform strings in nested objects and arrays in our index bounds.



 Comments   
Comment by Githook User [ 07/Jul/16 ]

Author:

{u'username': u'dhatch', u'name': u'David Hatch', u'email': u'david.hatch@mongodb.com'}

Message: SERVER-23172 Implement nested string translation iteratively.
Branch: master
https://github.com/mongodb/mongo/commit/23ded63a51236acc586ad0850f2359d6bcc02c97

Comment by Githook User [ 22/Jun/16 ]

Author:

{u'username': u'dhatch', u'name': u'David Hatch', u'email': u'david.hatch@mongodb.com'}

Message: SERVER-23172 Allow use of indices for collation-aware queries that match nested objects or arrays.
Branch: master
https://github.com/mongodb/mongo/commit/40f20eca105a5e06a72df583ac654f946e9b058e

Generated at Thu Feb 08 04:02:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.