Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
Storage NYC 2018-05-07
-
0
Description
In secondary_reads_timestamp_visibility.js we have loops like the following:
for (let i in levels) { |
// We should see the previous state on the secondary with every readconcern. |
assert.eq(secondaryDB.getCollection(collName).find({x: 0}).readConcern(levels[i]).itcount(),
|
0);
|
assert.eq(secondaryDB.getCollection(collName).find({x: 1}).readConcern(levels[i]).itcount(),
|
100);
|
}
|
We should update the assertion message to mention the read concern level being used for that find; otherwise it makes it difficult to determine what's failing.