GODRIVER-3285 Allow sort option in client bulk write. #1923
Conversation
API Change Report./v2/mongocompatible changes(*ClientReplaceOneModel).SetSort: added |
qingyang-hu
force-pushed
the
godriver3285clientBulkWrite
branch
from
ada2a32 to
24db535
Compare
mongo/client_bulk_write_models.go
Outdated
| @@ -105,6 +106,14 @@ func (uom *ClientUpdateOneModel) SetUpsert(upsert bool) *ClientUpdateOneModel { | |||
| return uom | |||
| } | |||
|
|
|||
| // SetSort specifies which document the operation updates if the query matches multiple documents. The first document | |||
| // matched by the sort order will be updated. This option is only valid for MongoDB versions >= 8.0. The driver will | |||
| // return an error if the sort parameter is a multi-key map. The default value is nil. | |||
There was a problem hiding this comment.
Suggest clarifying this sentence:
The driver will return an error if the sort parameter is a multi-key map.
Note that the sort parameter cannot be an unordered since different orders mean different things. Specifically, when sorting on multiple fields, sort order is evaluated from left to right.
Because sort order matters (evaluating left to right), the driver will return an error if the sort parameter is a multi-key map to prevent unintentional behavior.
SetSort for ClientReplaceOneModel also needs to be updated.
There was a problem hiding this comment.
I will update the comment for findoptions, too.
GODRIVER-3285
Summary
Allow sort option in
UpdateOneandRepleaceOnein client bulk write.Background & Motivation
Collection bulk write has been done in #1797