diff options
author | ADAM David Alan Martin <adam.martin@10gen.com> | 2018-03-01 16:40:51 -0500 |
---|---|---|
committer | ADAM David Alan Martin <adam.martin@10gen.com> | 2018-03-01 16:40:51 -0500 |
commit | 296fde1259d29e081069fde1c69bb9ae083932b1 (patch) | |
tree | 0e0973b0e6e642e09822f59be220be3a8c036466 /src/mongo/db/SConscript | |
parent | 22b2b828a922a7459b4e1c75860a11c7eb3db630 (diff) | |
download | mongo-296fde1259d29e081069fde1c69bb9ae083932b1.tar.gz |
SERVER-32843 Allow multiple times in OpObservers
The OpObserverRegistry was introduced as an abstraction to allow
decoupling making data modifications from the side effects, which
need to happen as a result of these modifications, such as op log
writes, retryable writes, etc.
Some of the OpObserver's methods currently return the OpTime which
resulted from logging the operation to the replication oplog. In
addition, in certain cases, the OpTime resulting from an earlier
OpObserver might be needed by a later one, which is the case with
retryable writes.
In order to support these requirements, the OpObserver(s) chain
should have access to some common per-operation structure, where
runtime information could be persisted.
Diffstat (limited to 'src/mongo/db/SConscript')
-rw-r--r-- | src/mongo/db/SConscript | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/src/mongo/db/SConscript b/src/mongo/db/SConscript index ed133252c5b..0145ab406d4 100644 --- a/src/mongo/db/SConscript +++ b/src/mongo/db/SConscript @@ -120,6 +120,8 @@ env.CppUnitTest( source= 'op_observer_registry_test.cpp', LIBDEPS=[ 'common', + 'op_observer', + 'service_context', ], ) @@ -645,12 +647,24 @@ env.Library( ) env.Library( + target="op_observer", + source=[ + "op_observer.cpp", + ], + LIBDEPS=[ + '$BUILD_DIR/mongo/base', + '$BUILD_DIR/mongo/util/decorable', + ], +) + +env.Library( target="op_observer_d", source=[ "op_observer_impl.cpp", ], LIBDEPS=[ 'catalog/collection_options', + 'op_observer', 'repl/oplog', 'views/views_mongod', '$BUILD_DIR/mongo/base', |