[
https://issues.apache.org/jira/browse/NIFI-7881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212582#comment-17212582
]
Matt Burgess commented on NIFI-7881:
------------------------------------
AFAIK ConvertAvroSchema is deprecated (as is the entire nifi-kite-nar) and not
being actively maintained. If the record-based processors (and
AvroReader/Writer) perform correctly, I recommend using that approach going
forward.
> Coercion problem with ConvertAvroSchema processor
> -------------------------------------------------
>
> Key: NIFI-7881
> URL: https://issues.apache.org/jira/browse/NIFI-7881
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.10.0, 1.9.2, 1.11.4, 1.12.1
> Reporter: Dominik Przybysz
> Priority: Major
>
> I have two schemas - input one has Map<String, UNION<null, String, Double>>
> field and output schema has the same field with type Map<String, UNION<null,
> String>>.
> In such example Double should be coerced to String, but it is still Double
> and processor fails to write avro object because of incompatible field type.
> I created two similar tests:
> - for AvroRecordConverter (used by ConvertAvroSchema) which fails
> - for AvroTypeUtil (used in some other components which write avro objects)
> and here the test passes
> The tests are here:
> https://github.com/alien11689/nifi/commit/87f890b33efd232297b79bbe19ba6cd05d36e614
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
