[
https://issues.apache.org/jira/browse/NIFI-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694014#comment-17694014
]
ASF subversion and git services commented on NIFI-11209:
--------------------------------------------------------
Commit 3e377d026323913bb7176205954e7c93ae1cf667 in nifi's branch
refs/heads/support/nifi-1.x from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3e377d0263 ]
NIFI-11209: Include newly-added columns in output for UpdateTable processors
when Update Field Names is true
Signed-off-by: Pierre Villard <[email protected]>
This closes #6986.
> UpdateHive3Table and UpdateDatabaseTable erase newly created columns in
> output FlowFile
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-11209
> URL: https://issues.apache.org/jira/browse/NIFI-11209
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using UpdateHive3Table or PutDatabaseTable with the Update Field Names
> property set to "true", the output will include only those fields that
> already had existing columns in the target table. This means if an incoming
> FlowFile has a "new" field, the column will be created and populated in the
> target database, but the output FlowFile will no longer have the "new" fields
> in the outgoing records.
> This is because the original database columns are used to populate the
> outgoing record schema when the Update Field Names property is set to true.
> Instead the database columns should be refreshed/maintained after any DDL is
> executed in order to get the updated set of database column names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
