nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Percivall (JIRA)" <j...@apache.org>
Subject [jira] [Created] (NIFI-4414) PutElasticsearch and PutElasticsearch5 should more granularly handle exceptions
Date Sun, 24 Sep 2017 23:18:00 GMT
Joseph Percivall created NIFI-4414:
--------------------------------------

             Summary: PutElasticsearch and PutElasticsearch5 should more granularly handle
exceptions
                 Key: NIFI-4414
                 URL: https://issues.apache.org/jira/browse/NIFI-4414
             Project: Apache NiFi
          Issue Type: Improvement
            Reporter: Joseph Percivall
            Priority: Minor


PutElasticsearch and PutElasticsearch5 have the same exception handling such that when an
exception occurs, any FlowFiles left in flowFilesToTransfer are transferred to failure (except
in a timeout scenario). This does not discriminate between errors that occur in the first
part (setting up the request by iterating over the FlowFiles) and the second part (checking
the individual responses for success or failure).

A good example of why this is deficient is if EL is used and the timestamp toDate function
is used with an improper format. This would cause an error to occur here[1] and then automatically
fail all the FlowFiles in the batch (default batch of 100), regardless if they would've succeeded
if actually run.

[1] https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-5-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearch5.java#L196



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message