nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-969) Add option to use standard JSON or Avro-JSON to ConvertAvroToJSON
Date Tue, 14 Feb 2017 21:46:41 GMT

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

ASF GitHub Bot commented on NIFI-969:
-------------------------------------

Github user olegz commented on the issue:

    https://github.com/apache/nifi/pull/1179
  
    The issue described in the underlying JIRA and this PR is essentially addressed or to
be addressed/maintained by a new Schema Registry based transformer effort - https://github.com/apache/nifi/pull/1436
    So, closing it and suggesting to close the underlying JIRA as well


> Add option to use standard JSON or Avro-JSON to ConvertAvroToJSON
> -----------------------------------------------------------------
>
>                 Key: NIFI-969
>                 URL: https://issues.apache.org/jira/browse/NIFI-969
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.3.0
>            Reporter: Ryan Blue
>            Assignee: Oleg Zhurakousky
>
> ConvertAvroToJSON uses {{GenericData#toString(GenericRecord)}} to convert to JSON. This
produces [Avro-JSON|https://avro.apache.org/docs/1.7.7/spec.html#json_encoding], which probably
isn't what most users want because it adds an unexpected layer for Avro union types:
> bq. the union schema {{["null","string",...]}} ... would encode: the string {{"a"}} as
{{{"string": "a"}}} ...
> It would be good to have a conversion that doesn't add those layers as an option.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message