[
https://issues.apache.org/jira/browse/NIFI-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762127#comment-15762127
]
ASF subversion and git services commented on NIFI-3194:
-------------------------------------------------------
Commit 8e3c4eb9a4246346f9b29b40933e3b7da556eb2c in nifi's branch
refs/heads/support/nifi-1.1.x from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8e3c4eb ]
NIFI-3194: Fixed error handling in PutElasticsearchHttp
Thise closes #1327
Signed-off-by: jpercivall <[email protected]>
> PutElasticsearchHttp should route flowfiles to failure on connection errors
> ---------------------------------------------------------------------------
>
> Key: NIFI-3194
> URL: https://issues.apache.org/jira/browse/NIFI-3194
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Fix For: 1.2.0, 1.1.1
>
>
> If PutElasticsearchHttp encounters connection errors with the specified URL
> (such as there is no server available at the specified hostname:port), a
> ProcessException is thrown and the session is rolled back.
> For other processors that accept input flow files and access a URL (such as
> PostHttp and InvokeHttp), if such an error occurs, the flow file(s) are
> routed to failure. PutElasticsearchHttp should have behavior consistent with
> the others, and if connection errors occur, any incoming flow files should be
> routed to failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
