diff options
author | Mathias Stearn <mathias@10gen.com> | 2018-07-25 17:33:21 -0400 |
---|---|---|
committer | Mathias Stearn <mathias@10gen.com> | 2018-07-30 14:13:08 -0400 |
commit | a5f3bf878d5059215fbc5a5a371aaf2d8a85e8b9 (patch) | |
tree | 86baac1bd319bbe02ca31c2404d0b631ff5a25ad /src/mongo/tools | |
parent | cca8ad6cf6f47e86158a8636b6a07743bd115fcc (diff) | |
download | mongo-a5f3bf878d5059215fbc5a5a371aaf2d8a85e8b9.tar.gz |
SERVER-33135 Remove metadata accessors from command reply APIs
Now that OP_COMMAND is dead, all remaining implementations return the same
BSONObj for data and metadata.
Diffstat (limited to 'src/mongo/tools')
-rw-r--r-- | src/mongo/tools/bridge.cpp | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/src/mongo/tools/bridge.cpp b/src/mongo/tools/bridge.cpp index 6938882953d..5793af94803 100644 --- a/src/mongo/tools/bridge.cpp +++ b/src/mongo/tools/bridge.cpp @@ -303,14 +303,12 @@ DbResponse ServiceEntryPointBridge::handleRequest(OperationContext* opCtx, const invariant(!isFireAndForgetCommand); auto replyBuilder = rpc::makeReplyBuilder(rpc::protocolForMessage(request)); - BSONObj metadata; BSONObj reply; StatusWith<BSONObj> commandReply(reply); if (!status->isOK()) { commandReply = StatusWith<BSONObj>(*status); } - return { - replyBuilder->setCommandReply(std::move(commandReply)).setMetadata(metadata).done()}; + return {replyBuilder->setCommandReply(std::move(commandReply)).done()}; } |