[
https://issues.apache.org/jira/browse/NIFI-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035952#comment-15035952
]
ASF GitHub Bot commented on NIFI-1234:
--------------------------------------
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/136#issuecomment-161330101
@trkurc
I am failing at the Github and JIRA comment game, but as commented on the
issue (and I am additionally editing myself for context here):
Sorry, missed some of your earlier comments (these were from last night
when you expanded the cases) in flipping between here and Github. Also hate the
property bloat, but think it is necessary to avoid the breaking change. Had a
hard time grokking the use cases that steered it away from bug status, so am
onboard with your viewpoint.
> 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
> Assignee: Aldrin Piri
> 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)
