[
https://issues.apache.org/jira/browse/NIFI-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933977#comment-16933977
]
ASF subversion and git services commented on NIFI-6691:
-------------------------------------------------------
Commit d0371a5ef1f1abe59b7f1de310f21fb93e8fbacb in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d0371a5 ]
NIFI-6691: This closes #3754. Fixed bug in MapRecord's algorithm for
incorporating Inactive Fields, by recursing into any 'child fields' that
contain records; also fixed bug in UpdateRecord that caused it to incorrectly
map the first result to all elements if the key of the property points to an
array
> UpdateRecord fails to update Record Schema when adding new "inner" field
> ------------------------------------------------------------------------
>
> Key: NIFI-6691
> URL: https://issues.apache.org/jira/browse/NIFI-6691
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If UpdateRecord is used to add a field to a Record, the output Record should
> have a schema that consists of the input record's schema modified to account
> for any newly added fields/types. For example, if the input Record contains 3
> fields, "street", "city", and "state", and a new field, "fullAddress" is to
> be added by UpdateRecord, the output Record should contain all 4 fields.
> This works already. But if the field to add is not at "root" level (for
> example, if the root is a Record that has an array of type Address that
> possesses all of these fields) then the resulting Record has a Schema with an
> "Address" field that still contains only street, city, and state – not the
> new "fullAddress" field.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
