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 2020/11/10 21:54:00 UTC

[jira] [Updated] (NIFI-7862) Allow PutDatabaseRecord to optionally create the target table if it doesn't exist

     [ https://issues.apache.org/jira/browse/NIFI-7862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-7862:
-------------------------------
    Description: 
As part of NIFI-6934, the "Database Type" property was added, allowing for DB-specific SQL/DML to be generated. That property could be used with a new true/false property "Create Table" that would create the target table if it didn't already exist. mapping the NiFi Record datatypes to DB-specific column types and generating/executing a DB-specific CREATE TABLE statement. If "Create Table" is set to true and an error occurs while attempting to create the table, the flowfile should be routed to failure or rolled back (depending on the setting of the "Rollback on Failure" property).

Also it could support some schema migration (adding columns, e.g.) with an additional value in the "Unmatched Field Behavior" property for "Create Column on Unmatched Fields". The use case here is for feature parity with UpdateHiveTable (see NIFI-7989)

  was:
As part of NIFI-6934, the "Database Type" property was added, allowing for DB-specific SQL/DML to be generated. That property could be used with a new true/false property "Create Table" that would create the target table if it didn't already exist.

I wouldn't go so far as to support schema migration (changing column types, e.g.), at least not for this case, the intent here would only be to check if table exists and attempt to create it , mapping the NiFi Record datatypes to DB-specific column types and generating/executing a DB-specific CREATE TABLE statement. If "Create Table" is set to true and an error occurs while attempting to create the table, the flowfile should be routed to failure or rolled back (depending on the setting of the "Rollback on Failure" property).


> Allow PutDatabaseRecord to optionally create the target table if it doesn't exist
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-7862
>                 URL: https://issues.apache.org/jira/browse/NIFI-7862
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Priority: Major
>
> As part of NIFI-6934, the "Database Type" property was added, allowing for DB-specific SQL/DML to be generated. That property could be used with a new true/false property "Create Table" that would create the target table if it didn't already exist. mapping the NiFi Record datatypes to DB-specific column types and generating/executing a DB-specific CREATE TABLE statement. If "Create Table" is set to true and an error occurs while attempting to create the table, the flowfile should be routed to failure or rolled back (depending on the setting of the "Rollback on Failure" property).
> Also it could support some schema migration (adding columns, e.g.) with an additional value in the "Unmatched Field Behavior" property for "Create Column on Unmatched Fields". The use case here is for feature parity with UpdateHiveTable (see NIFI-7989)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)