Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <347538963.15721267564047375.JavaMail.jira@brutus.apache.org>
Date: Tue, 2 Mar 2010 21:07:27 +0000 (UTC)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Updated: (AVRO-432) add java annotation to specify arbitrary
 schema
In-Reply-To: <288928421.541251267143267918.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AVRO-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting updated AVRO-432:
------------------------------

    Status: Patch Available  (was: Open)

> add java annotation to specify arbitrary schema
> -----------------------------------------------
>
>                 Key: AVRO-432
>                 URL: https://issues.apache.org/jira/browse/AVRO-432
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>    Affects Versions: 1.3.0
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.3.1
>
>         Attachments: AVRO-432.patch, AVRO-432.patch, AVRO-432.patch
>
>
> HDFS now includes a class (HdfsFileStatus) with a field (symlink) whose type is byte[] but which is null for non-symlinks.  For most other types, we could annotate this with something like @Union({Void.class, Foo.class}) to declare that the field may be null.  But there is unfortunately no way to refer to the class of byte[] in an annotation.  So, instead, I propose to add an annotation that permits the specification of an arbitrary schema.  In this case, the annotation would then be @AvroSchema("[\"null\",\bytes\"").

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