[
https://issues.apache.org/jira/browse/NIFI-14789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013297#comment-18013297
]
ASF subversion and git services commented on NIFI-14789:
--------------------------------------------------------
Commit 56a0fff50d0fbf0472e891ee9fd105d02422d07d in nifi's branch
refs/heads/main from tpalfy
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=56a0fff50d ]
NIFI-14789 Updated PutSQL to send invalid FlowFiles to failure (#10136)
- PutSQL routes FlowFiles without database.name to failure when a
FlowFileFilter is configured in the DBCPService implementation
- Updated DBCPConnectionPoolLookup FlowFileFilter to avoid throwing a
ProcessException
Signed-off-by: David Handermann <[email protected]>
> PutSQL doesn't handle invalid incoming FileFiles properly
> ---------------------------------------------------------
>
> 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)
