You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing out the CollectionOptions.encryptedCollection feature in Spring Data MongoDB version 4.5.0 with Queryable Encryption, I noticed that currently, it seems I can only encrypt fields that are also marked as queryable. However, in some use cases, I’d like to have fields that are encrypted but not queryable.
For example, I’d like to do something like this:
CollectionOptions collectionOptions = CollectionOptions.encryptedCollection(options -> options
.encrypted(encrypted(string("name")).keyId(dkName.asUuid())) // encrypted but not queryable
.queryable(encrypted(int32("age")).algorithm("Range").keyId(dkAge.asUuid()), range().contention(0).min(0).max(130)) // encrypted and queryable
);
This would allow me to encrypt the "name" field without making it queryable, while still taking advantage of range queries on "age". As of now, the API doesn’t seem to support this scenario.
Let me know if you need anything.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
mp911de
changed the title
Support for Non-Queryable Encrypted Fields in CollectionOptions
Support for Non-Queryable Encrypted Fields in CollectionOptionsJun 4, 2025
Fix Javadoc, make QueryCharacteristics a Streamable for easier usage during mapping, reformat code for reduced nesting levels.
See #4988
Original pull request: #4992
Fix Javadoc, make QueryCharacteristics a Streamable for easier usage during mapping, reformat code for reduced nesting levels.
See #4988
Original pull request: #4992
Uh oh!
There was an error while loading. Please reload this page.
Hi team,
While testing out the CollectionOptions.encryptedCollection feature in Spring Data MongoDB version 4.5.0 with Queryable Encryption, I noticed that currently, it seems I can only encrypt fields that are also marked as queryable. However, in some use cases, I’d like to have fields that are encrypted but not queryable.
For example, I’d like to do something like this:
This would allow me to encrypt the "name" field without making it queryable, while still taking advantage of range queries on "age". As of now, the API doesn’t seem to support this scenario.
Let me know if you need anything.
Thanks in advance.
The text was updated successfully, but these errors were encountered: