In some cases, an update command with the {upsert: true} flag could result in the server generating an _id field. If this is true, and the schema indicates that _id is encrypted, then mongocryptd must return an error. As part of this ticket we should also:
- Determine whether this work will be necessary for findAndModify, once mongocryptd also supports findAndModify.
- Confirm that the server does not choose new values for top-level Timestamp(0,0) for upserts. We believe this behavior is insert-specific, but we need to confirm.
- Confirm that full document replacement-style updates will autogenerate current time from Timestamp(0, 0).
- depends on
-
SERVER-39233 [FLE] Implement method for replacing elements in a MatchExpression with an encryption placeholder
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-