[NIFI-8146] Allow RecordPath to be used for specifying operation type and data fields when using PutDatabaseRecord

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.13.0
• Component/s: Extensions
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 15/Jan/21 19:36
• Updated: 09/May/24 18:15
• Resolved: 20/Jan/21 18:50

Description

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. 

Issue Links

• is duplicated by: NIFI-8004 PutDatabaseRecord doesn't route error flow file to failure and leaves it in the input queue
• links to: GitHub Pull Request #4763
• links to: GitHub Pull Request #4770