You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2021/01/19 18:26:00 UTC
[jira] [Updated] (NIFI-8146) Allow RecordPath to be used for
specifying operation type and data fields when using PutDatabaseRecord
[ https://issues.apache.org/jira/browse/NIFI-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-8146:
-------------------------------
Status: Patch Available (was: Open)
> 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
> Time Spent: 0.5h
> 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)