You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mike Thomsen (Jira)" <ji...@apache.org> on 2020/12/04 12:41:00 UTC
[jira] [Updated] (NIFI-6878) ConvertJSONToSQL Improvement.
Statement Type Support "Use statement.type Attribute" or Supports
Expression Language
[ https://issues.apache.org/jira/browse/NIFI-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Thomsen updated NIFI-6878:
-------------------------------
Fix Version/s: 1.13.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ConvertJSONToSQL Improvement. Statement Type Support "Use statement.type Attribute" or Supports Expression Language
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6878
> URL: https://issues.apache.org/jira/browse/NIFI-6878
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: ZhangCheng
> Assignee: Matt Burgess
> Priority: Minor
> Fix For: 1.13.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ConvertJSONToSQL Statement Type provides fixed options : UPDATE,INSERT,DELETE.
> Usually, it can meet our needs. But in actual application,I think It's not flexible enough.
> In some cases, we need to dynamically indicate the Statement Type.
> For example,the data from CpatureChangeMysql owns the attribute of statement type(cdc.event.type, we need to convert the data to sql(DML) orderly; And we now have to use RouteOnAttribute to transfer data to three branches , Build SQL statement separately ,finally,we have to use EnforceOrder to ensure the order of SQL statements.
> But it will be easy if ConvertJSONToSQL supports dynamical Statement Type .
> It is easy to implement this feature just like PutDatabaseRecord.
> In practice, I did use PutDatabaseRecord instead of ConvertJSONToSQL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)