Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Tue, 13 Oct 2015 20:59:05 +0000 (UTC)
From: "Ryan Blue (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12904603.1444756376000.28657.1444769945508@Atlassian.JIRA>
In-Reply-To: <JIRA.12904603.1444756376000@Atlassian.JIRA>
References: <JIRA.12904603.1444756376000@Atlassian.JIRA>
 <JIRA.12904603.1444756376134@arcas>
Subject: [jira] [Commented] (AVRO-1746) JSON encoder and decoder for Ruby
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ryan Blue commented on AVRO-1746:
---------------------------------

Sounds reasonable to me.

It should just be a matter of adding the encoder/decoder, but keep in mind that Avro's JSON encoding adds an extra layer for unions. That might be tricky for your third-party gems. There's another issue open to add a specification for using JSON that looks more like you might expect (including how you would handle union resolution), but that hasn't been completed worked on recently. Also, we should ensure there is a container format spec if you intend to write multiple JSON records to a stream.

> JSON encoder and decoder for Ruby
> ---------------------------------
>
>                 Key: AVRO-1746
>                 URL: https://issues.apache.org/jira/browse/AVRO-1746
>             Project: Avro
>          Issue Type: New Feature
>          Components: ruby
>            Reporter: Saroj Yadav
>
> Hi,
> I am thinking of adding a JSON encoder and decoder for Ruby. What do you think?
> Best,
> Saroj


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