[
https://issues.apache.org/jira/browse/NIFI-14789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-14789:
------------------------------------
Summary: PutSQL should route FlowFiles missing database.name to failure
when DBCP Service has a FlowFileFilter (was: PutSQL doesn't handle invalid
incoming FileFiles properly)
> PutSQL should route FlowFiles missing database.name to failure when DBCP
> Service has a FlowFileFilter
> -----------------------------------------------------------------------------------------------------
>
> Key: NIFI-14789
> URL: https://issues.apache.org/jira/browse/NIFI-14789
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Tamas Palfy
> Assignee: Tamas Palfy
> Priority: Major
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> PutSQL pre-screens FlowFiles by getting a FlowFileFilter from the configured
> 'JDBC Connection Pool'.
> If this FlowFileFilter throws an exception (like
> DBCPConnectionPoolLookup.getFlowFileFilter does), PutSQL rolls back the
> session.
> Because of this, the invalid FlowFiles will stay in the incoming queue
> forever (even if 'Rollback On Failure' is set to 'false') and stop the flow
> from working.
> FlowFiles deemed invalid during pre-screening should be considered faulty and
> routed to failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
