You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/05/10 15:50:00 UTC

[jira] [Commented] (NIFI-5045) PutHiveQL routes parse errors to retry instead of failure

    [ https://issues.apache.org/jira/browse/NIFI-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470585#comment-16470585 ] 

ASF subversion and git services commented on NIFI-5045:
-------------------------------------------------------

Commit 8f988c3b8a11f643e74580d08716d88090f6d143 in nifi's branch refs/heads/HDF-3.1-maint from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8f988c3 ]

NIFI-5045: Fixed error code handling in PutHiveQL. This closes #2608


> PutHiveQL routes parse errors to retry instead of failure
> ---------------------------------------------------------
>
>                 Key: NIFI-5045
>                 URL: https://issues.apache.org/jira/browse/NIFI-5045
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Minor
>             Fix For: 1.7.0
>
>
> When the input to PutHiveQL is an invalid HiveQL statement, the documentation for the failure relationship should apply: "A FlowFile is routed to this relationship if the database cannot be updated and retrying the operation will also fail, such as an invalid query or an integrity constraint violation". However, upon invalid HiveQL, the processor routes the flowfile to 'retry', which is neither desired or logical (the query is bad, how could it ever succeed on retry?)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)