Open bewood opened 5 years ago
I'm facing the same difficulties because of the missing msg
object.
This affects all nodes, not just DynamoDB. It is a problem for me, too, as I run these nodes from flows that are exposed as web services. Without the msg.res and msg.req data in the error, it is impossible to send a response to the original http request, so it must time out instead.
Expected
The error output of a DynamoDB node to add
msg.err
to existingmsg
object.Actual
The error output of a DynamoDB node is a new
msg
with onlymsg.err
and a newmsg._msgid
property.Impact
This causes issues using DynamoDB in an HTTP endpoint flow because it loses the
msg.res
object. Additionally, mitigations by stashingmsg.res
in flow context aren't possible because even themsg._msgid
is lost.