[COMPASS-6898] MongoDB Compass does not create an index in the KeyVault collection Created: 06/Jun/23 Updated: 28/Jun/23 |
|
| Status: | Open |
| Project: | Compass |
| Component/s: | Field Level Encryption |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Miguel Angel Nieto | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: MacOS |
||
| Story Points: | 3 |
| Description |
Problem Statement/RationaleWhat is going wrong? What action would you like the Engineering team to take? When creating the KeyVault for queryable encryption, Compass does not create the keyAltNames index, as documented here. As discussed in slack: > with CSFLE, we designed it to be able to handle millions of keys, so a vault index made sense. It won't hurt with QE, but definitely not high-priority. So, even if it is not high priority, it would be good both MongoDB Shell and MongoDB Compass uses the same structure and the index is created as documented. Steps to ReproduceHow could an engineer replicate the issue you’re reporting? Follow the procedure to create a quertyable encryption collection. Once done, check the indexes in the KeyVault, there will be none. Expected ResultsWhat do you expect to happen? There should be one index in keyAltNames similar to the one MongoDB Shell creates, as seen here. |