[DRIVERS-2407] Update expected error in fle2-InsertFind-Unindexed test Created: 30/Jul/22  Updated: 02/Aug/22

Status: Implementing
Project: Drivers
Component/s: Client Side Encryption
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kevin Albertson Assignee: Kevin Albertson
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CXX-2561 Update expected error in fle2-InsertF... Backlog
split to CDRIVER-4446 Update expected error in fle2-InsertF... Closed
split to CSHARP-4285 Update expected error in fle2-InsertF... Closed
split to GODRIVER-2512 Update expected error in fle2-InsertF... Closed
split to MOTOR-1010 Update expected error in fle2-InsertF... Closed
split to NODE-4490 Update expected error in fle2-InsertF... Closed
split to PHPLIB-930 Update expected error in fle2-InsertF... Closed
split to PYTHON-3386 Update expected error in fle2-InsertF... Closed
split to RUBY-3075 Update expected error in fle2-InsertF... Closed
split to RUST-1430 Update expected error in fle2-InsertF... Closed
split to JAVA-4699 Update expected error in fle2-InsertF... Closed
Driver Changes: Needed
Downstream Changes Summary:

Resync the fle2-InsertFind-Unindexed test to https://github.com/mongodb/specifications/commit/1a911b5e8911f6f57426ec1d451dbdc19480afd8

This updates the error message assertion to account for recent error message changes server-side.

Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4446 Fixed 1.23.0, 1.22.2
CXX-2561 Backlog
CSHARP-4285 Fixed 2.18.0
GODRIVER-2512 Fixed 1.10.1
JAVA-4699 Fixed 4.7.2
NODE-4490 Fixed 4.9.0
MOTOR-1010 Duplicate
PYTHON-3386 Duplicate
PHPLIB-930 Fixed 1.15.0
RUBY-3075 Fixed 2.19.0
RUST-1430 Duplicate
SWIFT-1621 Duplicate

 Description   

Summary

Update the expected error message in fle2-InsertFind-Unindexed.yml to account a recent change in query analysis: https://github.com/10gen/mongo-enterprise-modules/commit/212b584d4f7a44bed41c826a180a4aff00923d7a#diff-5f12b55e8d5c52c2f62853ec595dc2c1e2e5cb4fdbf7a32739a8e3acb3c6f818

Motivation

Who is the affected end user?

DBX engineers.

How does this affect the end user?

"latest" tests will fail.

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

Definitely.

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

Test failures.

Is this issue urgent?

Yes.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.


Generated at Thu Feb 08 08:25:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.