[
https://issues.apache.org/jira/browse/NIFI-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120056#comment-15120056
]
Oleg Zhurakousky commented on NIFI-1443:
----------------------------------------
Aaron, thanks for filing it, but I am thinking there may be some duplication as
something similar appears to be reported and tracked via NIFI-1093. Could you
please look at it and see if one of these two JIRAs could be marked as
duplicate?
> ConvertJSONToSQL - INSERT with subset of required columns
> ---------------------------------------------------------
>
> Key: NIFI-1443
> URL: https://issues.apache.org/jira/browse/NIFI-1443
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.1
> Environment: Ubuntu Server 14.04 LTS
> Reporter: Aaron Stephens
> Labels: ConvertJSONToSQL, JSON, SQL
> Fix For: 0.4.1
>
>
> I've ran into a rather annoying bug with the ConvertJSONToSQL processor. I
> have a table in a postgresql db with a set of columns, most of which are
> required. However, several of the required columns are populated via BEFORE
> INSERT triggers based on other columns. NiFi, trying to save me from myself,
> sees that I have not supplied it with all of the required columns, and the
> FlowFile fails.
> For a very simple example, say I have a table with columns A, B, and C; all
> integers and all required. I have a BEFORE INSERT trigger set to assign C
> with the sum of A and B. I can perform an INSERT with just columns A and B,
> and let the trigger handle column C. But NiFi doesn't like this, probably
> because it has no way of knowing about triggers.
> Is there any way I can disable this check? Or is INSERTING a subset of
> required columns simply not supported?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
