ExtensionCallMarkLogic sends to success when REST call responds 500

[s3-4v]

I'm working on a project with a client, and we're experiencing this apparent bug:

Using ExtensionCallMarkLogic proc to POST to Data Hub REST extension mlRunFlow, when the response status code is 500 Internal Server Error, the FlowFile is being routed to the success relationship.

The InvokeHTTP proc making the same call to the same resource sends to failure queue and only routes to the equivalent of success when the status code is 2xx, the expected behavior.

NiFi 1.11.4
MarkLogic NARS 1.9.1.3-incubator
MarkLogic 10.0-4
MarkLogic Data Hub 5.2.1

[rjrudin]

This may be resolved in marklogic/nifi via marklogic/nifi#103 . I say "may be" because if the request is that ExtensionCallML should analyze the JSON response from the DHF mlRunFlow endpoint to determine if there are errors, I don't think that should be done - ExtensionCallML should not have knowledge of responses from particular endpoints. Instead, a subsequent processor should do that analysis. I recommend closing this if that's what this ticket is asking for.