Description
When I run below through eventing server, all requests return success though many N1QL statements failed.
function OnUpdate(doc,meta) {
|
log("Trying:", meta.id);
|
try {
|
UPDATE dst AS d USE KEYS "k01" SET d = d+1;
|
log("Success:", meta.id)
|
} catch (e) {
|
log("Exception:", e)
|
}
|
}
|
I verified this with wireshark:
HTTP/1.0 200 OK
|
{
|
"requestID": "f6e08658-c092-4a02-bda6-ed065621a7a4",
|
"results": [
|
],
|
"errors": [{"code":12009,"msg":"DML Error, possible causes include CAS mismatch or concurrent modificationFailed to perform update - cause: MCResponse status=KEY_EEXISTS, opcode=SET, opaque=0, msg: "}],
|
"status": "errors",
|
}
|
But the handler throws no exception when above happens.
Attachments
Issue Links
- is a backport of
-
MB-32060 N1QL exception not bring propagated
-
- Closed
-
| For Gerrit Dashboard: MB-32316 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 102670,5 | [MB-32316] Backport: Conditionally parse to check for N1QL error | alice | eventing | Status: MERGED | +2 | +1 |