Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Wed, 24 May 2017 14:18:05 +0000 (UTC)
From: "MihkelJ (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12739954.1410205729000.283558.1495635485118@Atlassian.JIRA>
In-Reply-To: <JIRA.12739954.1410205729000@Atlassian.JIRA>
References: <JIRA.12739954.1410205729000@Atlassian.JIRA> <JIRA.12739954.1410205729566@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AVRO-1582) Json serialization of nullable
 fileds and fields with default values improvement.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 24 May 2017 14:18:11 -0000


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

MihkelJ commented on AVRO-1582:
-------------------------------

We ran up against this issue recently, so I've created a standalone encoder from Zoltan Farkas' excellent ExtendedJsonDecoder, until this issue is resolved: https://github.com/Celos/avro-json-decoder

It handles point b) from above, infers the value of missing fields from their defaults. The only advantage is that it doesn't require forked avro.

> Json serialization of nullable fileds and fields with default values improvement.
> ---------------------------------------------------------------------------------
>
>                 Key: AVRO-1582
>                 URL: https://issues.apache.org/jira/browse/AVRO-1582
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.8.0
>            Reporter: Zoltan Farkas
>         Attachments: AVRO-1582-PATCH
>
>
> Currently serializing a nullable field of type union like:
> "type" : ["null","some type"]
> when serialized as JSON results in:  
> "field":{"some type":"value"}
> when it could be:
> "field":"value"
> Also fields that equal the the default value can be omitted from the serialized data. This is possible because the reader will have the writer's schema and can infer the field values. This reduces the size of the json messages.


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