Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <647103149.1240606230528.JavaMail.jira@brutus>
Date: Fri, 24 Apr 2009 13:50:30 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Commented: (AVRO-17) remove single float type
In-Reply-To: <1976305449.1240595130681.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-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702546#action_12702546 ] 

Doug Cutting commented on AVRO-17:
----------------------------------

> perhaps removing it now isn't required, since we can back-compatibly re-define it with a standard library...

I take that back.  For back-compatibily, we'd want the standard library definitions to always be included in the schema stored in files and sent over the wire: a runtime should only have to know about the primitives and compound types.  So having "float" without a definition in a data file wouldn't let us later remove this as a primitve and replace it in runtimes by a standard library.

> remove single float type
> ------------------------
>
>                 Key: AVRO-17
>                 URL: https://issues.apache.org/jira/browse/AVRO-17
>             Project: Avro
>          Issue Type: Improvement
>          Components: spec
>            Reporter: Doug Cutting
>             Fix For: 1.0
>
>
> Python and Thrift do not support a 32-bit single float type, nor do many applications use this type, so, for better compatibility, we can remove it from Avro.

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