Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <1646606660.1254904711340.JavaMail.jira@brutus>
Date: Wed, 7 Oct 2009 01:38:31 -0700 (PDT)
From: "Sharad Agarwal (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Commented: (AVRO-80) 'reflect' implementation requires Avro
 classes to define types
In-Reply-To: <712192656.1248061574794.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sharad Agarwal commented on AVRO-80:
------------------------------------

I think there should be a default and easy way to work with Strings. I came across couple of instances where potential users enquired about this and this limitation deterred them to use Avro.
Should we make the reflect *default* representation of String schema as java.lang.String itself? I agree that performance is the concern but I think for reflect that trade-off is fine.

> 'reflect' implementation requires Avro classes to define types
> --------------------------------------------------------------
>
>                 Key: AVRO-80
>                 URL: https://issues.apache.org/jira/browse/AVRO-80
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>            Reporter: Sharad Agarwal
>
> Since 'reflect' implementation is expected to work with existing code, it should work with java types. For example it should work with java String instead of org.apache.avro.util.Utf8.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.