Summary

MONGOCRYPT-793 changes libmongocrypt to no longer error under the scenario:

• Doing a $lookup operation
• Using a QE schema and a non-CSFLE JSON Schema.
• Using mongocryptd/crypt_shared 8.2+ (including SERVER-100260)

Motivation

Previously, libmongocrypt returned an explanatory error due to limitations in server < 8.2. SERVER-100260 now permits mixing QE and non-CSFLE JSON schemas.

Who is the affected end user?

CSFLE/QE users wanting to do $lookup.

How does this affect the end user?

Permits doing $lookup in more cases on server 8.2+.

How likely is it that this problem or use case will occur?

Likely? The current behavior prevents doing a $lookup on QE against a collection with a non-CSFLE JSON schema configured.

If the problem does occur, what are the consequences and how severe are they?

Drivers testing 8.2+ may fail after upgrading to libmongocrypt containing MONGOCRYPT-793. Case 8: db.csfle joins db.qe expects a string error returned from libmongocrypt.

Is this issue urgent?

Somewhat? Drivers will need to do this before upgrading to libmongocrypt containing MONGOCRYPT-793 to avoid test failures.

Is this ticket required by a downstream team?

No?

Is this ticket only for tests?

Mostly yes. Drivers only need to upgrade libmongocrypt and update tests.

Acceptance Criteria

• Update Case 8: db.csfle joins db.qe to support testing with server 8.2+ and libmongocrypt containing MONGOCRYPT-793.
• Add a test for the happy-path case: test $lookup mixing a non-CSFLE JSON schema and QE works against server 8.2+.