INTPYTHON-527 Add Queryable Encryption support #329

aclark4life · 2025-06-27T02:16:28Z

Previous attempts and additional context here:

INTPYTHON-527 Add Queryable Encryption config #318
- Branched from transaction support and includes only helpers
INTPYTHON-527 Add queryable encryption support #319
- In which this bug in libmongocrypt was discovered
- A fix for that bug in PyMongo is being discussed here.
INTPYTHON-527 Add Queryable Encryption support #323
- Before I understood that the shared lib for mongocrypt was included in the pymongocrypt wheel.

tests/encryption_/tests.py

django_mongodb_backend/models.py

django_mongodb_backend/encryption.py

django_mongodb_backend/schema.py

django_mongodb_backend/base.py

django_mongodb_backend/fields/encryption.py

django_mongodb_backend/schema.py

django_mongodb_backend/features.py

django_mongodb_backend/routers.py

django_mongodb_backend/schema.py

django_mongodb_backend/fields/encryption.py

django_mongodb_backend/schema.py

tests/encryption_/tests.py

tests/encryption_/routers.py

tests/encryption_/models.py

tests/backend_/test_features.py

django_mongodb_backend/schema.py

tests/encryption_/models.py

django_mongodb_backend/schema.py

django_mongodb_backend/encryption.py

tests/encryption_/routers.py

django_mongodb_backend/schema.py

django_mongodb_backend/models.py

django_mongodb_backend/management/commands/get_encrypted_fields_map.py

docs/source/ref/encryption.rst

django_mongodb_backend/fields/encryption.py

django_mongodb_backend/management/commands/get_encrypted_fields_map.py

django_mongodb_backend/schema.py

tests/encryption_/tests.py

django_mongodb_backend/encryption.py

django_mongodb_backend/utils.py

docs/source/howto/encryption.rst

django_mongodb_backend/schema.py

django_mongodb_backend/management/commands/get_encrypted_fields_map.py

docs/source/ref/models/fields.rst

django_mongodb_backend/utils.py

django_mongodb_backend/features.py

docs/source/ref/models/fields.rst

tests/backend_/test_features.py

tests/encryption_/models.py

tests/backend_/test_features.py

Jibola

I've added my first round of comments. I haven't looked over the tests yet but plan to do so next week. A big area I'll dig more into is around the discussion on KMS_PROVIDERS and KMS_CREDENTIALS

Jibola · 2025-07-28T17:02:32Z

django_mongodb_backend/base.py

+        # Avoid using PyMongo to check the database version or require
+        # pymongocrypt>=1.14.2 which will contain a fix for the `buildInfo`
+        # command. https://jira.mongodb.org/browse/PYTHON-5429
+        return tuple(self.connection.admin.command("buildInfo")["versionArray"])


One caveat is depending on auth status, the admin and commands may not be available.

That would apply to the PyMongo API as well. This change only addresses the libmongocrypt issue that we have not worked around in PyMongo.

Jibola · 2025-08-01T19:59:27Z

django_mongodb_backend/routers.py

+def kms_provider(self, model, *args, **kwargs):
+    for router in self.routers:
+        func = getattr(router, "kms_provider", None)
+        if func and callable(func):
+            result = func(model, *args, **kwargs)
+            if result is not None:
+                return result
+    if getattr(model, "encrypted", False):
+        raise ImproperlyConfigured("No kms_provider found in database router.")


So this allows a KMS_PROVIDER to be defined at the Database Router level? Why not let it only be something done in the settings.py?

create_encrypted_collection() takes the kms_provider argument, so this allows the provider to be selected per model, if needed. If that level of granularity isn't required, we can re-think the API.

Considering we're already enforcing a separate database for encrypted collections, I think it's best to keep it at the granularity of the database. Then, a model would defer to the custom routing for the kms provider. It seems excessive to have multiple KMS providers just for a collection.

As well, since there's no way to compare encrypted keys across collections, having multiple databases in the configuration still feels like the right way to go.

If customers end up needing this fulfilled I can accept that, but even in that case, they could just have database level configurations.

No, I wouldn't say that this is per database router, but it is per database. It could be a Django setting, but why set a KMS_PROVIDER in Django when you only really need it for the encrypted database. The per-model flexibility is a function of database routers, not a function of KMS provider configuration and folks could take advantage of that ability for this feature or any feature in which a custom router is configured.

Jibola · 2025-08-01T20:02:04Z

django_mongodb_backend/fields/encryption.py

+# TODO: Add more encrypted fields
+# - PositiveBigIntegerField
+# - PositiveIntegerField
+# - PositiveSmallIntegerField
+# - SmallIntegerField


Make a JIRA to track this TODO

Added everything but PositiveIntegerField which seems to have some issue with being a long in MongoDB.

Jibola · 2025-08-01T20:03:09Z

django_mongodb_backend/encryption.py

+        if model:
+            return db == ("other" if has_encrypted_fields(model) else "default")
+        return db == "default"
+
+    def db_for_read(self, model, **hints):
+        if has_encrypted_fields(model):
+            return "other"
+        return "default"
+
+    db_for_write = db_for_read
+
+    def kms_provider(self, model):
+        return "local"


should these be hard-coded to database name? Or is this just an example.

To me, this is an example that should be moved to the docs.

All of the above. The local provider is for local testing and the other database was because @WaVEV had previously used an other database for cache testing.

Jibola · 2025-08-01T20:06:32Z

django_mongodb_backend/features.py

+        self.connection.ensure_connection()
+        client = self.connection.connection.admin
+        build_info = client.command("buildInfo")
+        is_enterprise = "enterprise" in build_info.get("modules")


cc: @ShaneHarvey is this guaranteed to capture enterprise connections?

I believe @JamesKovacs confirmed this

Enterprise 07895885-9f55-4ee3-a362-4a06a321aefa [direct: secondary] test> db.adminCommand("buildInfo") { version: '8.1.1', versionArray: [ 8, 1, 1, 0 ], gitVersion: 'c441b67d7260844c1422bf259e23c054a33ee7d8', modules: [ 'enterprise' ], …

django_mongodb_backend/schema.py

docs/source/howto/queryable-encryption.rst

tests/backend_/test_features.py

django_mongodb_backend/management/commands/get_encrypted_fields_map.py

timgraham · 2025-08-01T22:35:13Z

django_mongodb_backend/routers.py

+def kms_provider(self, model, *args, **kwargs):
+    for router in self.routers:
+        func = getattr(router, "kms_provider", None)
+        if func and callable(func):
+            result = func(model, *args, **kwargs)
+            if result is not None:
+                return result
+    if getattr(model, "encrypted", False):
+        raise ImproperlyConfigured("No kms_provider found in database router.")


create_encrypted_collection() takes the kms_provider argument, so this allows the provider to be selected per model, if needed. If that level of granularity isn't required, we can re-think the API.

timgraham · 2025-08-01T22:35:47Z

django_mongodb_backend/encryption.py

+        if model:
+            return db == ("other" if has_encrypted_fields(model) else "default")
+        return db == "default"
+
+    def db_for_read(self, model, **hints):
+        if has_encrypted_fields(model):
+            return "other"
+        return "default"
+
+    db_for_write = db_for_read
+
+    def kms_provider(self, model):
+        return "local"


To me, this is an example that should be moved to the docs.

docs/source/howto/queryable-encryption.rst

tests/backend_/test_features.py

timgraham · 2025-08-01T22:46:26Z

django_mongodb_backend/management/commands/get_encrypted_fields_map.py

+                        data_key = ce.create_data_key(
+                            kms_provider=kms_provider,
+                            master_key=master_key,
+                        )


I commented on the design doc, where I was hoping you could say whether or not this is even needed. It's present in the Automatic Queryable Encryption example, but this doesn't follow that example since key_alt_names isn't present.

timgraham · 2025-08-02T01:15:20Z

docs/source/intro/install.rst

+If you plan to use :doc:`/topics/queryable-encryption/`, you will also need to install
+the optional dependencies:
+
+.. code-block:: bash
+
+    $ pip install --pre django-mongodb-backend[encryption]==5.2.*


I'd omit this here. This won't be relevant to most users reading the introductory installation documentation and you correctly mentioned it in the encryption howto.

timgraham · 2025-08-02T01:23:04Z

docs/source/topics/known-issues.rst

+Queryable Encryption
+====================
+
+Consider these
+`limitations and restrictions <https://www.mongodb.com/docs/manual/core/queryable-encryption/reference/limitations/>`_
+before enabling Queryable Encryption. Some operations are unsupported, and others behave differently.
+
+Also see :ref:`unsupported fields <encrypted-fields-unsupported-fields>`.


Really this known-issues.rst page is limitations of Django's core features. I think we can keep limitations and problems with MongoDB specific features on their respective pages (e.g. there is some of that with EmbeddedModelField: schema changes not supported, etc.).

timgraham · 2025-08-02T01:25:37Z

tests/encryption_/tests.py

+        # FIXME: Or remove if wontfix.
+        #
+        # This test fails due to
+        # pymongo.errors.OperationFailure: Index not allowed on, or a prefix
+        # of, the encrypted field slug
+        with self.assertRaises(AssertionError):  # noqa: SIM117
+            with self.assertRaises(pymongo.errors.OperationFailure):
+
+                class SlugFieldTest(models.Model):
+                    slug = EncryptedSlugField(EqualityQuery())


I believe the issue is that SlugField has db_index=True. Slugs are generally used in URLs and it seems they would generally not be sensitive data that needs to be encrypted.

The limitation that encrypted fields can't be indexed seems a point worth documenting.

I'm not sure if they can't be indexed or if they are auto indexed. The docs say

Queryable Encryption does not support TTL Indexes or Unique Indexes.

timgraham · 2025-08-02T01:28:33Z

docs/source/topics/known-issues.rst

+Consider these
+`limitations and restrictions <https://www.mongodb.com/docs/manual/core/queryable-encryption/reference/limitations/>`_
+before enabling Queryable Encryption. Some operations are unsupported, and others behave differently.


I was hoping for a translation of how those restrictions apply to Django querysets, etc. Quickly scanning that page, it reads as MongoDB mumbo jumbo that's meaningless to Djangonauts.

The tutorial only demonstrates find_one and I've been using get in the tests. I'm not sure if filter and/or lookups are going to work.

timgraham · 2025-08-02T23:39:06Z

The encryption tests are passing locally for me on Enterprise and on the Atlas VM.

On GitHub actions, this first issue was solved by adding "directConnection": True in DATABASES:

  File "/home/runner/work/django-mongodb-backend/django-mongodb-backend/django_repo/django/db/backends/base/base.py", line 197, in check_database_version_supported
    and self.get_database_version() < self.features.minimum_database_version
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/django-mongodb-backend/django-mongodb-backend/django_mongodb_backend/base.py", line 235, in get_database_version
    return tuple(self.connection.admin.command("buildInfo")["versionArray"])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/_csot.py", line 125, in csot_wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/database.py", line 926, in command
    with self._client._conn_for_reads(read_preference, session, operation=command_name) as (
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/mongo_client.py", line 1864, in _conn_for_reads
    server = self._select_server(read_preference, session, operation)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/mongo_client.py", line 1812, in _select_server
    server = topology.select_server(
             ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 409, in select_server
    server = self._select_server(
             ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 387, in _select_server
    servers = self.select_servers(
              ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 294, in select_servers
    server_descriptions = self._select_servers_loop(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 344, in _select_servers_loop
    raise ServerSelectionTimeoutError(
pymongo.errors.ServerSelectionTimeoutError: Could not reach any servers in [('3ff0eef351ff', 27017)]. Replica set is configured with internal hostnames or IPs?, Timeout: 30s, Topology Description: <TopologyDescription id: 688e9488ca8c88d98365da45, topology_type: ReplicaSetNoPrimary, servers: [<ServerDescription ('3ff0eef351ff', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('3ff0eef351ff:27017: [Errno -3] Temporary failure in name resolution (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>

But this issue remains:

Creating test database for alias 'encrypted' ('test_djangotests-encrypted')...
/home/runner/.local/lib/python3.12/site-packages/pymongo/daemon.py:147: RuntimeWarning: Failed to start mongocryptd: is it on your $PATH?
Original exception: [Errno 2] No such file or directory: 'mongocryptd'
  _silence_resource_warning(_spawn(sys.argv[1:]))
/home/runner/.local/lib/python3.12/site-packages/pymongo/daemon.py:147: RuntimeWarning: Failed to start mongocryptd: is it on your $PATH?
Original exception: [Errno 2] No such file or directory: 'mongocryptd'
  _silence_resource_warning(_spawn(sys.argv[1:]))
  Applying sites.0002_alter_domain_unique... OK
Operations to perform:
  Synchronize unmigrated apps: auth, contenttypes, encryption_, messages, sessions, staticfiles
  Apply all migrations: admin, sites
Synchronizing apps without migrations:
  Creating tables...
    Creating table encryption__appointment
Traceback (most recent call last):
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/encryption.py", line 286, in mark_command
    res = self.mongocryptd_client[database].command(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/_csot.py", line 125, in csot_wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/database.py", line 926, in command
    with self._client._conn_for_reads(read_preference, session, operation=command_name) as (
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/mongo_client.py", line 1864, in _conn_for_reads
    server = self._select_server(read_preference, session, operation)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/mongo_client.py", line 1812, in _select_server
    server = topology.select_server(
             ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 409, in select_server
    server = self._select_server(
             ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 387, in _select_server
    servers = self.select_servers(
              ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 294, in select_servers
    server_descriptions = self._select_servers_loop(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/pymongo/synchronous/topology.py", line 344, in _select_servers_loop
    raise ServerSelectionTimeoutError(
pymongo.errors.ServerSelectionTimeoutError: localhost:27020: [Errno 111] Connection refused (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 10.0s, Topology Description: <TopologyDescription id: 688e9f76697ba6965a378048, topology_type: Unknown, servers: [<ServerDescription ('localhost', 27020) server_type: Unknown, rtt: None, error=AutoReconnect('localhost:27020: [Errno 111] Connection refused (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>

timgraham · 2025-08-02T21:38:47Z

tests/encryption_/tests.py

+        self.assertEqual(
+            PatientRecord.objects.get(ssn="123-45-6789").profile_picture, b"image data"
+        )
+        with self.assertRaises(AssertionError):


What's your thinking about the usefulness of this assertion? If assertEqual(profile_picture, b"image data") passed, then of course asserting it's not equal to something else is going to work? (Incidentally, assertNotEqual() is more natural than assertEqual() + assertRaises().)

More generally, it seems like you weren't sure exactly what to test here, so you wrote various things that came to mind. Maybe we need to define the test conditions so we can have some more standardized testing.

Since we're relying on the encryption algorithm to detect changes I wanted to see it pass and fail, and yes the plan was to add fields to the patient-themed test suite, expanding on the tutorial example.

timgraham · 2025-08-02T23:03:00Z

tests/encryption_/tests.py

+            # FIXME: pymongo.errors.EncryptionError: Cannot encrypt element of type int
+            # because schema requires that type is one of: [ long ]
+            # pos_int=1,


The data type for each field is determined by this mapping:

django-mongodb-backend/django_mongodb_backend/base.py

Lines 36 to 63 in d5aa1a7

data_types = {

"AutoField": "int",

"BigAutoField": "long",

"BinaryField": "binData",

"BooleanField": "bool",

"CharField": "string",

"DateField": "date",

"DateTimeField": "date",

"DecimalField": "decimal",

"DurationField": "long",

"FileField": "string",

"FilePathField": "string",

"FloatField": "double",

"IntegerField": "int",

"BigIntegerField": "long",

"GenericIPAddressField": "string",

"JSONField": "object",

"OneToOneField": "int",

"PositiveBigIntegerField": "int",

"PositiveIntegerField": "long",

"PositiveSmallIntegerField": "int",

"SlugField": "string",

"SmallAutoField": "int",

"SmallIntegerField": "int",

"TextField": "string",

"TimeField": "date",

"UUIDField": "string",

}

It seems the mapping has some mistakes. For example, PositiveBigIntegerField should be long (64-bit) [I think]. That said, this is an issue that should be correct in a separate PR.

The question remains how to send the value to the database as a long to avoid this error. Frankly, I wouldn't expect any special handling to be needed, but maybe Jib has some idea. (Was this already discussed when you ran into the error for DurationField?)

It has not been discussed and now that you mention it, DurationField may have been similar.

aclark4life commented Jun 27, 2025

View reviewed changes

tests/encryption_/tests.py Outdated Show resolved Hide resolved

aclark4life commented Jun 27, 2025

View reviewed changes

django_mongodb_backend/models.py Outdated Show resolved Hide resolved

aclark4life commented Jun 27, 2025

View reviewed changes

django_mongodb_backend/encryption.py Outdated Show resolved Hide resolved

timgraham reviewed Jun 27, 2025

View reviewed changes

This comment was marked as resolved.

Sign in to view

timgraham reviewed Jun 30, 2025

View reviewed changes

django_mongodb_backend/features.py Outdated Show resolved Hide resolved

timgraham reviewed Jul 1, 2025

View reviewed changes

django_mongodb_backend/routers.py Outdated Show resolved Hide resolved

timgraham reviewed Jul 1, 2025

View reviewed changes

django_mongodb_backend/schema.py Outdated Show resolved Hide resolved

This comment was marked as resolved.

Sign in to view

timgraham reviewed Jul 4, 2025

View reviewed changes

tests/encryption_/models.py Show resolved Hide resolved

timgraham reviewed Jul 7, 2025

View reviewed changes

tests/encryption_/models.py Outdated Show resolved Hide resolved

aclark4life commented Jul 7, 2025

View reviewed changes

django_mongodb_backend/schema.py Outdated Show resolved Hide resolved

This comment was marked as resolved.

Sign in to view

timgraham reviewed Jul 9, 2025

View reviewed changes

tests/encryption_/tests.py Outdated Show resolved Hide resolved

tests/encryption_/tests.py Outdated Show resolved Hide resolved

tests/encryption_/tests.py Outdated Show resolved Hide resolved

This comment was marked as resolved.

Sign in to view

aclark4life commented Jul 11, 2025

View reviewed changes

tests/encryption_/tests.py Outdated Show resolved Hide resolved

This comment was marked as resolved.

Sign in to view

timgraham reviewed Jul 22, 2025

View reviewed changes

addaleax reviewed Jul 25, 2025

View reviewed changes

django_mongodb_backend/features.py Show resolved Hide resolved

django_mongodb_backend/features.py Outdated Show resolved Hide resolved

aclark4life requested review from a team, Copilot, timgraham and WaVEV July 25, 2025 20:08

This comment was marked as resolved.

Sign in to view

aclark4life force-pushed the INTPYTHON-527 branch from 2d672f2 to 10ae20e Compare July 31, 2025 16:10

timgraham reviewed Jul 31, 2025

View reviewed changes

docs/source/ref/models/fields.rst Outdated Show resolved Hide resolved

docs/source/ref/models/fields.rst Outdated Show resolved Hide resolved

tests/backend_/test_features.py Outdated Show resolved Hide resolved

tests/encryption_/models.py Outdated Show resolved Hide resolved

aclark4life force-pushed the INTPYTHON-527 branch from 4acc5ab to 796855e Compare August 1, 2025 19:37

timgraham removed request for a team and WaVEV August 1, 2025 21:42

timgraham force-pushed the INTPYTHON-527 branch from affa499 to 29a1d97 Compare August 1, 2025 21:59

aclark4life commented Aug 1, 2025

View reviewed changes

tests/backend_/test_features.py Show resolved Hide resolved

Jibola reviewed Aug 1, 2025

View reviewed changes

timgraham reviewed Aug 1, 2025

View reviewed changes

aclark4life force-pushed the INTPYTHON-527 branch from 89205af to 293656a Compare August 1, 2025 23:16

timgraham reviewed Aug 2, 2025

View reviewed changes

aclark4life force-pushed the INTPYTHON-527 branch from 270727c to f0d4e92 Compare August 2, 2025 03:04

INTPYTHON-527 Add Queryable Encryption support

4ef6b84

aclark4life force-pushed the INTPYTHON-527 branch from f0d4e92 to 4ef6b84 Compare August 2, 2025 15:02

timgraham force-pushed the INTPYTHON-527 branch 3 times, most recently from 6e1b8ed to 3815a70 Compare August 2, 2025 22:41

timgraham added 2 commits August 2, 2025 19:27

fix encrypted tests

9954a7c

[debug] skip most tests for now

a6a12e7

timgraham force-pushed the INTPYTHON-527 branch from 3815a70 to a6a12e7 Compare August 2, 2025 23:28

timgraham reviewed Aug 2, 2025

View reviewed changes

	data_types = {
	"AutoField": "int",
	"BigAutoField": "long",
	"BinaryField": "binData",
	"BooleanField": "bool",
	"CharField": "string",
	"DateField": "date",
	"DateTimeField": "date",
	"DecimalField": "decimal",
	"DurationField": "long",
	"FileField": "string",
	"FilePathField": "string",
	"FloatField": "double",
	"IntegerField": "int",
	"BigIntegerField": "long",
	"GenericIPAddressField": "string",
	"JSONField": "object",
	"OneToOneField": "int",
	"PositiveBigIntegerField": "int",
	"PositiveIntegerField": "long",
	"PositiveSmallIntegerField": "int",
	"SlugField": "string",
	"SmallAutoField": "int",
	"SmallIntegerField": "int",
	"TextField": "string",
	"TimeField": "date",
	"UUIDField": "string",
	}

INTPYTHON-527 Add Queryable Encryption support #329

Are you sure you want to change the base?

INTPYTHON-527 Add Queryable Encryption support #329

Conversation

aclark4life commented Jun 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

Uh oh!

Uh oh!

Uh oh!

This comment was marked as resolved.

This comment was marked as resolved.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment was marked as resolved.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Jibola left a comment

aclark4life commented Jun 27, 2025 •

edited

Loading

aclark4life Aug 1, 2025 •

edited

Loading