You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/06/12 01:33:00 UTC

[jira] [Commented] (NIFI-6370) Allow PutDatabaseRecord to execute multiple SQL statements if using SQL field

    [ https://issues.apache.org/jira/browse/NIFI-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861656#comment-16861656 ] 

ASF subversion and git services commented on NIFI-6370:
-------------------------------------------------------

Commit 05f3cadee8ee76aa05a1d35ffb4598ddeca4f549 in nifi's branch refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=05f3cad ]

NIFI-6370: Allow multiple SQL statements in PutDatabaseRecord

This closes #3528.

Signed-off-by: Koji Kawamura <ij...@apache.org>


> Allow PutDatabaseRecord to execute multiple SQL statements if using SQL field
> -----------------------------------------------------------------------------
>
>                 Key: NIFI-6370
>                 URL: https://issues.apache.org/jira/browse/NIFI-6370
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> PutDatabaseRecord can be configured to point at a field in a record that contains a SQL statement, and execute the statement rather than a generated INSERT/UPDATE/DELETE statement from the fields in the record.  It would be helpful if the SQL field could contain multiple SQL statements (delimited by semicolons) and each of the statements be executed, rolling back the whole thing if any errors occur.
> To maintain current behavior, I propose adding a boolean property to "Allow Multiple SQL Statements" that is only used when the statement type is SQL. This is also necessary because we can't fully parse the SQL statements; instead we can just split the SQL field by semicolons (like PutHiveQL does).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)