[
https://issues.apache.org/jira/browse/NIFI-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura resolved NIFI-5832.
---------------------------------
Resolution: Duplicate
[~bdesert] I believe this is a duplicate with NIFI-5834. I tested the example
queries in this JIRA's description while I'm reviewing NIFI-5834, too. With
NIFI-5834, FlowFiles are routed to 'failure' relationship as expected.
> PutHiveQL - Flowfile isn't transferred to failure rel on actual failure
> -----------------------------------------------------------------------
>
> Key: NIFI-5832
> URL: https://issues.apache.org/jira/browse/NIFI-5832
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Ed Berezitsky
> Assignee: Ed Berezitsky
> Priority: Major
>
> PutHiveQL is stuck if error occurred when flow file contains multiple
> statements.
> Example:
>
> {code:java}
> set tez.queue.name=qwe;
> create table t_table1 (s string) stored as orc;{code}
>
> This will fail if such queue doesn't exist. But FF will be stuck in incoming
> connection forever without even emitting bulletin (bulletin will appear only
> when the processor is in debug mode).
> Another example:
> {code:java}
> insert into table t_table1 select 'test' from test limit 1;
> insert into table non_existing_table select * from another_table;{code}
> Note, first statement is correct one, second should fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
