[
https://issues.apache.org/jira/browse/NIFI-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romeo Kienzer updated NIFI-8122:
--------------------------------
Summary: Support "upsert" functionality in ConvertJSONtoSQL processor
(was: Support "upsert" functionality in PutSQL processor)
> Support "upsert" functionality in ConvertJSONtoSQL processor
> ------------------------------------------------------------
>
> Key: NIFI-8122
> URL: https://issues.apache.org/jira/browse/NIFI-8122
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.12.1
> Reporter: Romeo Kienzer
> Priority: Major
>
> The ConvertJSONtoSQL processor doesn't Support "upsert" functionality, only
> insert, update and delete. As the ConvertJSONtoSQL already has a working jdbc
> connection to query metadata on the target table I think it would be
> straightforward to query the target table to decide if on a given row in a
> flow file an insert or an update has to be created.
> I don't know if I'm getting something completely wrong here, but the Nifi
> community only speaks about "workarounds" when it comes to upsert. So this
> way we would have a clean implementation (although it requires one additional
> query roundtrip per row), but at least there should be an index on the key
> fields
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
