[
https://issues.apache.org/jira/browse/NIFI-8512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340410#comment-17340410
]
ASF subversion and git services commented on NIFI-8512:
-------------------------------------------------------
Commit 2895bac2c088aa66c8b86ecba680f80e1323105a in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2895bac ]
NIFI-8512: When converting to/from Avro UNION type, we can be more efficient
when the UNION consists of a Null type and one other type by determinine the
non-null type and just using that. Also eliminated a call to List.stream() and
related .collect() call by using an existing method that performs the logic
without the very expensive call to stream()
Signed-off-by: Matthew Burgess <[email protected]>
This closes #5051
> NiFi is not efficient when handling nullable types with Avro Reader/Writer
> --------------------------------------------------------------------------
>
> Key: NIFI-8512
> URL: https://issues.apache.org/jira/browse/NIFI-8512
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using the Avro Reader/Writer any time we encounter nullable types, the
> AvroTypeUtil uses rather expensive logic that is necessary for many UNION
> cases but can be avoided in the case of UNION with NULL and one other data
> type.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
