[
https://issues.apache.org/jira/browse/NIFI-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268778#comment-17268778
]
ASF subversion and git services commented on NIFI-8146:
-------------------------------------------------------
Commit 803ba882aa15142a9986dc0c23bbf4db11fe15a7 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=803ba88 ]
NIFI-8146: Ensure that we close the Connection/Statement/PreparedStatement
objects in finally blocks or try-with-resources
Signed-off-by: Matthew Burgess <[email protected]>
This closes #4770
> Allow RecordPath to be used for specifying operation type and data fields
> when using PutDatabaseRecord
> ------------------------------------------------------------------------------------------------------
>
> Key: NIFI-8146
> URL: https://issues.apache.org/jira/browse/NIFI-8146
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> PutDatbaseRecord requires that the Statement Type be defined as a property or
> a FlowFile attribute. This means that if a FlowFile has many records, it must
> be split apart into individual Records if there is more than 1 type of
> statement needed per FlowFile.
> It also assumes that the data to be inserted/updated/deleted/etc is the full
> record. However, it's common to have some wrapper around the actual data, as
> is the case with a tool like Debezium, which includes an Operation Type, a
> 'before' snapshot and an 'after' snapshot. To accommodate this, we should
> allow Record-friendly methods for specifying the path to the data and the
> operation type.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
