MongoDB Bulkwrite which queries failed at match step?
I am doing bulkwrite operation in MongoDB to update multiple documents at a time.
Now Is there any way by which I can know which sequence number of my queries match step failed.
Because in returned document I am getting nModified
, nMatched
which tells how many match failed, but not which query sequence number got failed?
mongodb bulk-operations
add a comment |
I am doing bulkwrite operation in MongoDB to update multiple documents at a time.
Now Is there any way by which I can know which sequence number of my queries match step failed.
Because in returned document I am getting nModified
, nMatched
which tells how many match failed, but not which query sequence number got failed?
mongodb bulk-operations
1
In short, No. You only get counts. These are not "errors" so there is deemed to be no need report them or at which index of the batch a0
was returned. A very common usage pattern is to actually send several update requests where you really only expect "one" of those to actually match and do anything. So it's not as if it's a high demand feature. If you think you need this, then you would not be sending requests in bulk, and simply sending individual requests and inspecting the results. This is the price of admission.
– Neil Lunn
Nov 23 '18 at 6:24
add a comment |
I am doing bulkwrite operation in MongoDB to update multiple documents at a time.
Now Is there any way by which I can know which sequence number of my queries match step failed.
Because in returned document I am getting nModified
, nMatched
which tells how many match failed, but not which query sequence number got failed?
mongodb bulk-operations
I am doing bulkwrite operation in MongoDB to update multiple documents at a time.
Now Is there any way by which I can know which sequence number of my queries match step failed.
Because in returned document I am getting nModified
, nMatched
which tells how many match failed, but not which query sequence number got failed?
mongodb bulk-operations
mongodb bulk-operations
asked Nov 22 '18 at 23:37
Sudhanshu GaurSudhanshu Gaur
2,73122248
2,73122248
1
In short, No. You only get counts. These are not "errors" so there is deemed to be no need report them or at which index of the batch a0
was returned. A very common usage pattern is to actually send several update requests where you really only expect "one" of those to actually match and do anything. So it's not as if it's a high demand feature. If you think you need this, then you would not be sending requests in bulk, and simply sending individual requests and inspecting the results. This is the price of admission.
– Neil Lunn
Nov 23 '18 at 6:24
add a comment |
1
In short, No. You only get counts. These are not "errors" so there is deemed to be no need report them or at which index of the batch a0
was returned. A very common usage pattern is to actually send several update requests where you really only expect "one" of those to actually match and do anything. So it's not as if it's a high demand feature. If you think you need this, then you would not be sending requests in bulk, and simply sending individual requests and inspecting the results. This is the price of admission.
– Neil Lunn
Nov 23 '18 at 6:24
1
1
In short, No. You only get counts. These are not "errors" so there is deemed to be no need report them or at which index of the batch a
0
was returned. A very common usage pattern is to actually send several update requests where you really only expect "one" of those to actually match and do anything. So it's not as if it's a high demand feature. If you think you need this, then you would not be sending requests in bulk, and simply sending individual requests and inspecting the results. This is the price of admission.– Neil Lunn
Nov 23 '18 at 6:24
In short, No. You only get counts. These are not "errors" so there is deemed to be no need report them or at which index of the batch a
0
was returned. A very common usage pattern is to actually send several update requests where you really only expect "one" of those to actually match and do anything. So it's not as if it's a high demand feature. If you think you need this, then you would not be sending requests in bulk, and simply sending individual requests and inspecting the results. This is the price of admission.– Neil Lunn
Nov 23 '18 at 6:24
add a comment |
1 Answer
1
active
oldest
votes
You can use BulkWriteResult.writeErrors. It is available in both ordered and unordered mode of operation. Specifically, the "op" field will tell you the document that failed.
Here is a sample output from pymongo reference:
{'nInserted': 0,
'nMatched': 1,
'nModified': 1,
'nRemoved': 0,
'nUpserted': 0,
'upserted': ,
'writeConcernErrors': ,
'writeErrors': [{u'code': 11000,
u'errmsg': u'...E11000...duplicate key error...',
u'index': 1,
u'op': {'_id': 4}}]}
I want to know whether query found any doc or not, so it won't come in errors.
– Sudhanshu Gaur
Nov 23 '18 at 9:16
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439102%2fmongodb-bulkwrite-which-queries-failed-at-match-step%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can use BulkWriteResult.writeErrors. It is available in both ordered and unordered mode of operation. Specifically, the "op" field will tell you the document that failed.
Here is a sample output from pymongo reference:
{'nInserted': 0,
'nMatched': 1,
'nModified': 1,
'nRemoved': 0,
'nUpserted': 0,
'upserted': ,
'writeConcernErrors': ,
'writeErrors': [{u'code': 11000,
u'errmsg': u'...E11000...duplicate key error...',
u'index': 1,
u'op': {'_id': 4}}]}
I want to know whether query found any doc or not, so it won't come in errors.
– Sudhanshu Gaur
Nov 23 '18 at 9:16
add a comment |
You can use BulkWriteResult.writeErrors. It is available in both ordered and unordered mode of operation. Specifically, the "op" field will tell you the document that failed.
Here is a sample output from pymongo reference:
{'nInserted': 0,
'nMatched': 1,
'nModified': 1,
'nRemoved': 0,
'nUpserted': 0,
'upserted': ,
'writeConcernErrors': ,
'writeErrors': [{u'code': 11000,
u'errmsg': u'...E11000...duplicate key error...',
u'index': 1,
u'op': {'_id': 4}}]}
I want to know whether query found any doc or not, so it won't come in errors.
– Sudhanshu Gaur
Nov 23 '18 at 9:16
add a comment |
You can use BulkWriteResult.writeErrors. It is available in both ordered and unordered mode of operation. Specifically, the "op" field will tell you the document that failed.
Here is a sample output from pymongo reference:
{'nInserted': 0,
'nMatched': 1,
'nModified': 1,
'nRemoved': 0,
'nUpserted': 0,
'upserted': ,
'writeConcernErrors': ,
'writeErrors': [{u'code': 11000,
u'errmsg': u'...E11000...duplicate key error...',
u'index': 1,
u'op': {'_id': 4}}]}
You can use BulkWriteResult.writeErrors. It is available in both ordered and unordered mode of operation. Specifically, the "op" field will tell you the document that failed.
Here is a sample output from pymongo reference:
{'nInserted': 0,
'nMatched': 1,
'nModified': 1,
'nRemoved': 0,
'nUpserted': 0,
'upserted': ,
'writeConcernErrors': ,
'writeErrors': [{u'code': 11000,
u'errmsg': u'...E11000...duplicate key error...',
u'index': 1,
u'op': {'_id': 4}}]}
answered Nov 23 '18 at 2:38
BajalBajal
2,39911218
2,39911218
I want to know whether query found any doc or not, so it won't come in errors.
– Sudhanshu Gaur
Nov 23 '18 at 9:16
add a comment |
I want to know whether query found any doc or not, so it won't come in errors.
– Sudhanshu Gaur
Nov 23 '18 at 9:16
I want to know whether query found any doc or not, so it won't come in errors.
– Sudhanshu Gaur
Nov 23 '18 at 9:16
I want to know whether query found any doc or not, so it won't come in errors.
– Sudhanshu Gaur
Nov 23 '18 at 9:16
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439102%2fmongodb-bulkwrite-which-queries-failed-at-match-step%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
In short, No. You only get counts. These are not "errors" so there is deemed to be no need report them or at which index of the batch a
0
was returned. A very common usage pattern is to actually send several update requests where you really only expect "one" of those to actually match and do anything. So it's not as if it's a high demand feature. If you think you need this, then you would not be sending requests in bulk, and simply sending individual requests and inspecting the results. This is the price of admission.– Neil Lunn
Nov 23 '18 at 6:24