[SERVER-68636] Rename `HighCardinalityMode` to be more descriptive Created: 08/Aug/22  Updated: 29/Oct/23  Resolved: 10/Aug/22

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

Type: Task Priority: Major - P3
Reporter: Davis Haupt (Inactive) Assignee: Davis Haupt (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QO 2022-08-22
Participants:

 Description   

Right now there's some confusion between high cardinality/low selectivity and what that mode actually means for the server-side rewrite. This ticket will rename the mode to EncryptedCollScanMode to be more explicit about what the modes actually do: Rewriting to a $in makes use of the underlying multikey btree index on safecontent, while generating tags at runtime will answer the query with a column scan.



 Comments   
Comment by Githook User [ 10/Aug/22 ]

Author:

{'name': 'Davis Haupt', 'email': 'davis.haupt@mongodb.com', 'username': 'davish'}

Message: SERVER-68636 rename HighCardinalityMode to EncryptedCollScanMode
Branch: master
https://github.com/mongodb/mongo/commit/cd10f966669131d9efdc202f444c41fb2d5afd18

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