You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Douglas Doughty (JIRA)" <ji...@apache.org> on 2015/12/01 20:26:11 UTC

[jira] [Created] (NIFI-1234) Inconsistent container options in ConvertAvroToJSON

Douglas Doughty created NIFI-1234:
-------------------------------------

             Summary: Inconsistent container options in ConvertAvroToJSON
                 Key: NIFI-1234
                 URL: https://issues.apache.org/jira/browse/NIFI-1234
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core UI
    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)