[SERVER-63006] CSFLE - $facet aggregation fails on non-encrypted collection Created: 26/Jan/22  Updated: 21/Mar/22  Resolved: 21/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Phil Boardman Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: external-user
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on NODE-3907 Investigate NODE-3906 - CSFLE - $face... Closed
Related
Participants:

 Description   

What problem are you facing?

Connection has CSFLE configured with encryption on 2 collections. Attempting to use a $facet aggregation on a non-encrypted collection throws the following error:

"Aggregation stage [UNKNOWN] is not allowed or supported with automatic encryption"

What driver and relevant dependency versions are you using?

"mongodb": "4.1.1",

Steps to reproduce?



 Comments   
Comment by Eric Sedor [ 21/Mar/22 ]

Thank you for understanding, Phil. I'm going to close this ticket.

Comment by Phil Boardman [ 10/Mar/22 ]

@eric.sedor, contacted Atlas support. Also, verified that the behavior is the same in mongosh.

Comment by Eric Sedor [ 08/Mar/22 ]

Thanks phil@bestinclasscare.com. Since there are considerations unique to Atlas involved in the support of this feature, I'd like to ask that you reach out to our Atlas team to describe the issues you are having. You can do this by clicking the round green button at the bottom right of the cluster view page in Atlas.

It's possible this behavior is the ultimate result of a server bug, in which case we would address it here in the SERVER jira project. But Atlas support will be the best place to start to determine if a change is required in the core MongoDB server.

Comment by Phil Boardman [ 08/Mar/22 ]

@eric.sedor that is correct

Comment by Eric Sedor [ 08/Mar/22 ]

Hi phil@bestinclasscare.com, and thanks for your patience. I am inferring that you are using the "automatic encryption" feature that is provided in MongoDB Enterprise and on MongoDB Atlas. Is that right?

Comment by Phil Boardman [ 17/Feb/22 ]

I see there is an upgrade available on Atlas (5.0). Is it known whether this is fixed in 5.0?

Comment by Phil Boardman [ 01/Feb/22 ]

@eric.sedor 4.1.1 is the client driver version.

MongoDB version isĀ 4.4.12 (Atlas)

Comment by Eric Sedor [ 31/Jan/22 ]

Hi phil@bestinclasscare.com, can you clarify what version of MongoDB you are seeing this issue with? I am currently inferring that "4.4.1" is your node driver version, but let me know if I've misunderstood.

Comment by Neal Beeken [ 26/Jan/22 ]

Hi phil@bestinclasscare.com I identified the error comes from mongocryptd, so the issue isn't specifically related to the Nodejs driver, I've went ahead and redirected this to the server team to assist.

Comment by PM Bot [ 26/Jan/22 ]

Hi phil@bestinclasscare.com, thank you for submitting this ticket! The team is going to investigate in the linked NODE ticket and reply back to you here with more info after the investigation is completed.

Generated at Thu Feb 08 05:56:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.