diff options
| author | David Storch <david.storch@mongodb.com> | 2020-03-23 15:54:10 -0400 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2020-03-26 19:07:14 +0000 |
| commit | d0b52ddd66d7e9d79ff5d46a35d760a328464da7 (patch) | |
| tree | 6376b547bd71cc98072258cdc6e9036f69b86996 /src/mongo/db/ops | |
| parent | bcbae014e202d0ed38da00406df5b2a00d70eb03 (diff) | |
| download | mongo-d0b52ddd66d7e9d79ff5d46a35d760a328464da7.tar.gz | |
SERVER-41873 Remove most remaining uses of 'oplogReplay' flag
Starting in 4.4, this flag is accepted by the server but
does not affect how the query is executed. However, there
were several places in the code base where 'oplogReplay'
needed to be handled due to the possibility of a mixed
version 4.2/4.4 cluster. This logic can now be removed,
since a 4.6 node need not be compatible with 4.2.
In order to avoid breaking old drivers, the 'oplogReplay'
find command option and OP_QUERY flag bit will continue to
be accepted but ignored.
Diffstat (limited to 'src/mongo/db/ops')
| -rw-r--r-- | src/mongo/db/ops/write_ops_retryability.cpp | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/src/mongo/db/ops/write_ops_retryability.cpp b/src/mongo/db/ops/write_ops_retryability.cpp index 57e872fdb39..d39dc6f78c5 100644 --- a/src/mongo/db/ops/write_ops_retryability.cpp +++ b/src/mongo/db/ops/write_ops_retryability.cpp @@ -108,10 +108,8 @@ BSONObj extractPreOrPostImage(OperationContext* opCtx, const repl::OplogEntry& o : oplog.getPostImageOpTime().value(); DBDirectClient client(opCtx); - auto oplogDoc = client.findOne(NamespaceString::kRsOplogNamespace.ns(), - opTime.asQuery(), - nullptr, - QueryOption_OplogReplay); + auto oplogDoc = + client.findOne(NamespaceString::kRsOplogNamespace.ns(), opTime.asQuery(), nullptr); uassert(40613, str::stream() << "oplog no longer contains the complete write history of this " |