[SERVER-63950] Disallow creation of indexes over encrypted fields or prefix of an encrypted field Created: 23/Feb/22 Updated: 29/Oct/23 Resolved: 25/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Nicholas Zolnierz |
| 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-04-04 |
| Participants: |
| Description |
|
As part of this task, we should explore options for more complex queries than just equality to an encrypted field (e.g. conjunctions/disjunctions) |
| Comments |
| Comment by Githook User [ 24/Mar/22 ] |
|
Author: {'name': 'Nicholas Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}Message: |
| Comment by Nicholas Zolnierz [ 24/Mar/22 ] |
|
This ticket's original title was to disallow hinting with an index over an encrypted field, but after offline discussion we agreed to ban creating such indexes in the first place so a hint would fail with a "no index found" error. |