[
https://issues.apache.org/jira/browse/NIFI-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977853#comment-16977853
]
ASF subversion and git services commented on NIFI-5970:
-------------------------------------------------------
Commit b3880a4a067915c56aa3d1b602717eab7ffa02fb in nifi's branch
refs/heads/master from Koji Kawamura
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b3880a4 ]
NIFI-5970 Handle multiple input FlowFiles at Put.initConnection
Signed-off-by: Matthew Burgess <[email protected]>
This closes #3583
> PutSQL with batch size > 1 + DBCPConnectionPoolLookup results in missing
> database.name
> --------------------------------------------------------------------------------------
>
> Key: NIFI-5970
> URL: https://issues.apache.org/jira/browse/NIFI-5970
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.8.0
> Reporter: Bryan Bende
> Assignee: Koji Kawamura
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When the batch size is greater than 1 we end up passing null for the
> attributes that get passed in to the DBCPConnectionPoolLookup, this is
> because the attributes of each flow file could be different:
> [https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/pattern/Put.java#L97]
> Part of the issue is that at this point in the code we have no idea if we are
> using a DBCPConnectionPoolLookup that requires the database.name attribute,
> or just a regular DBCPConnectionPool that doesn't.
> https://stackoverflow.com/questions/54312773/dbcpconnectionpoollookup-complaining-about-missing-database-name-even-when-it-is
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
