[SERVER-42520] Auto encryption of a $changeStream aggregation fails with obscure error Created: 30/Jul/19  Updated: 29/Oct/23  Resolved: 10/Sep/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.2.0-rc4
Fix Version/s: 4.2.1, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Shane Harvey Assignee: Bernard Gorman
Resolution: Fixed Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Query 2019-09-09, Query 2019-09-23
Participants:

 Description   

mongocryptd returns the following error message when given a $changeStream pipeline:

{'ok': 0.0, 'errmsg': 'The $changeStream stage is only supported on replica sets', 'code': 40573, 'codeName': 'Location40573'}

It would be nicer if it returned an error stating that the $changeStream stage is not supported with auto encryption.

CC kevin.albertson.



 Comments   
Comment by Githook User [ 16/Sep/19 ]

Author:

{'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com', 'name': 'Bernard Gorman'}

Message: SERVER-42520 Set no-op replication co-ordinator on mongocryptd to allow parsing of change stream aggregations

(cherry picked from commit 89ae7560b6c9e93ed60b5b2c24e139218a6ea66c)
Branch: v4.2
https://github.com/10gen/mongo-enterprise-modules/commit/eabf9379c19634042b2349fb35778232c65d7c06

Comment by Githook User [ 10/Sep/19 ]

Author:

{'name': 'Bernard Gorman', 'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com'}

Message: SERVER-42520 Set no-op replication co-ordinator on mongocryptd to allow parsing of change stream aggregations
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/89ae7560b6c9e93ed60b5b2c24e139218a6ea66c

Comment by Kenneth White [ 05/Aug/19 ]

If the work isn't unrealistically burdensome, a clearer message would reduce Support load & troubleshooting. If we can get this in before GA, I think we should.

Comment by Nicholas Zolnierz [ 01/Aug/19 ]

I think this should live on the query backlog for now as it's an error coming from the query analysis on mongocryptd.

CC mark.benvenuto david.storch

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