[jira] [Commented] (NIFI-1234) Inconsistent container behavior in ConvertAvroToJSON

["Aldrin Piri (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034751#comment-15034751 ] 

Aldrin Piri commented on NIFI-1234:
-----------------------------------

Douglas,

I would agree that this seems to be a bit of an odd ball given the addition of the container property.  I am going to create a patch/PR on Github to get the behavior I would anticipate and reach out to the person who added this functionality.

> Inconsistent container behavior in ConvertAvroToJSON
> ----------------------------------------------------
>
>                 Key: NIFI-1234
>                 URL: https://issues.apache.org/jira/browse/NIFI-1234
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 0.4.0
>            Reporter: Douglas Doughty
>            Priority: Minor
>
> ConvertAvroToJSON has 2 container options: array and none.
> When set to 'array', usage dictates an "array of objects" should be produced.  But, if only a single Avro record is passed in, an array is not created--a JSON object is created.
> I believe it should be wrapped in an array.  This caused errors when chained with SplitJSON (which expects an array).
> Use case scenario:  ExecuteSQL returns an unknown number of results -> ConvertAvroToJSON -> SplitJSON.  If ExecuteSQL returns 1 result, then the operation fails.
> Work around: Set up a failure relationship between SplitJSON and the next processor--the object will be forwarded, but an error will be logged on the SplitJSON processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)