Commit Graph

10 Commits

Author SHA1 Message Date
James Wahlin
39c3a5d77b SERVER-42773 Replace uses of the assert.writeOK() Javascript assertion with assert.commandWorked() 2019-08-14 13:52:59 +00:00
clang-format-7.0.1
134a408395 SERVER-41772 Apply clang-format 7.0.1 to the codebase 2019-07-27 11:02:23 -04:00
James Wahlin
358c0af2fe SERVER-33727 Do not wait for write concern if opTime didn't change during write 2019-05-23 10:05:59 -04:00
Max Hirschhorn
35b5b72146 SERVER-32522 Clean up {read,write}Concern and readPreference overrides.
Introduces OverrideHelpers object with convenience methods for
inspecting certain aggregation and map-reduce commands, as well as
overriding startParallelShell(), Mongo.prototype.runCommand(), and
Mongo.prototype.runCommandWithMetadata().

Also removes a number of tests that were incorrectly blacklisted from
the read_concern_majority_passthrough.yml and
read_concern_linearizable_passthrough.yml test suites.
2018-01-30 19:45:42 -05:00
Jack Mulrow
00d92ece19 SERVER-31194 Add jscore tags for retryable_writes_jscore_stepdown_passthrough.yml suite
The actual suite will come in a follow-up commit.
2017-12-07 14:36:15 -05:00
Kyle Suarez
03945fa420 SERVER-28558 tests must not use jsTest.name() as a collection name
Doing so will cause tests to use the same collection in the parallel suite, where the name of the
test could be "basicPlus".
2017-03-31 11:35:12 -04:00
Eddie Louie
9fc1ecd711 SERVER-26315 Override DBCollection.prototype.drop to re-shard collections that are dropped
This reverts commit fb956b3b0a.
2017-03-23 14:07:50 -04:00
Randolph Tan
fb956b3b0a Revert "SERVER-26315 Override DBCollection.prototype.drop to re-shard collections that are dropped"
This reverts commit 56e66454d1.

Conflicts:
	buildscripts/resmokeconfig/suites/sharded_collections_jscore_passthrough.yml
2017-03-23 13:56:21 -04:00
Eddie Louie
56e66454d1 SERVER-26315 Override DBCollection.prototype.drop to re-shard collections that are dropped
in sharded cluster environments.
2017-03-15 19:19:49 -04:00
David Storch
82b16740f8 SERVER-19758 add support for "executionStats" and "allPlansExecution" to agg explain
Like other explainable commands, aggregate can now be
explained using the explain command, e.g.
db.runCommand({explain: {aggregate: ...}, verbosity:
"executionStats"}). The existing explain:true flag
corresponds to "queryPlanner" mode and is still supported.
However, explain:true cannot be specified when explaining
aggregate via the explain command.

Additional execution information is provided only in the
$cursor section of the aggregation explain output. Having
aggregation stages themselves track and report execution
info is further work.
2017-03-13 09:46:14 -04:00