|
In lieu of any code changes, let's add a documentation example for this usage. Linking to a docs ticket.
|
|
This is the same behavior as gle:
db.runCommand({getLastError:1, writeConcern:1})
|
{
|
"lastOp" : Timestamp(0, 0),
|
"connectionId" : 1,
|
"n" : 0,
|
"syncMillis" : 0,
|
"writtenTo" : null,
|
"err" : null,
|
"ok" : 1
|
}
|
I do agree we can do better with validation, but we should fix it all at once. Pretty sure this issue already exists, much like validating command args.
|
|
Seems like an issue with the Bulk interface in the shell.
|
|
It's also an issue that if you pass an invalid writeConcern parameter, you get no error. Passing the same badness to the getLastError command results in an error, I believe.
|
|
Uploaded a fixed test, and it passes. I think we have test coverage for this already, but if not it might be good to add it in a sep. issue.
|
|
I think this is a problem with the documentation: http://docs.mongodb.org/manual/reference/method/Bulk.execute/#Bulk.execute
It mentions a "writeConcern" parameter but it's not obvious that that is the documentation's name for it, not the key name actually used.
|
|
This js test is wrong. The arg to execute should be
, not
I think this is completely invalid.
|
Generated at Thu Feb 08 03:36:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.