summaryrefslogtreecommitdiff
path: root/src/mongo/db/SConscript
diff options
context:
space:
mode:
authorDaniel Gottlieb <daniel.gottlieb@mongodb.com>2022-02-08 10:36:43 -0500
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2022-02-08 16:34:26 +0000
commitdf441f20aab3ec13d30ab157d5761d419edc2051 (patch)
tree2ed95f188156356792878a2397dfb9538be32790 /src/mongo/db/SConscript
parent1938ca8564fb969f68058d68c55f632eec78a665 (diff)
downloadmongo-df441f20aab3ec13d30ab157d5761d419edc2051.tar.gz
SERVER-63308: Accomodate WT-8601.
Move read timestamp visibility against the oplog into MongoDB. WiredTiger historically loses timestamp information across restarts on logged tables. MDB does rely on read_timestamps for visibility against the oplog in some circumstances. While case analysis supports that the WT bug does not manifest in MDB, WT-8601 fully removes timestamps from `WT_UPDATE`s in logged tables. In MDB, the keys for oplog documents are the object's timestamp. MDB will instead use that value to filter an oplog entry's visibilty.
Diffstat (limited to 'src/mongo/db/SConscript')
-rw-r--r--src/mongo/db/SConscript1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/mongo/db/SConscript b/src/mongo/db/SConscript
index d56608b9032..49dd3a75584 100644
--- a/src/mongo/db/SConscript
+++ b/src/mongo/db/SConscript
@@ -2018,6 +2018,7 @@ env.Library(
'$BUILD_DIR/mongo/db/storage/ephemeral_for_test/storage_ephemeral_for_test',
'$BUILD_DIR/mongo/db/storage/storage_control',
'$BUILD_DIR/mongo/db/storage/storage_options',
+ '$BUILD_DIR/mongo/util/clock_source_mock',
'index_builds_coordinator_mongod',
'service_context_d',
],