Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Tue, 7 Jul 2015 17:56:05 +0000 (UTC)
From: "Ryan Blue (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12842944.1436205402000.120177.1436291765104@Atlassian.JIRA>
In-Reply-To: <JIRA.12842944.1436205402000@Atlassian.JIRA>
References: <JIRA.12842944.1436205402000@Atlassian.JIRA>
 <JIRA.12842944.1436205402256@arcas>
Subject: [jira] [Commented] (AVRO-1692) Allow more than one logical type for
 a Java class
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ryan Blue commented on AVRO-1692:
---------------------------------

I can add tests as part of AVRO-1672, or I can add the circular reference test that I posted to the mailing list for Sachin. Either one demonstrates the problem.

> Allow more than one logical type for a Java class
> -------------------------------------------------
>
>                 Key: AVRO-1692
>                 URL: https://issues.apache.org/jira/browse/AVRO-1692
>             Project: Avro
>          Issue Type: Task
>          Components: java
>            Reporter: Ryan Blue
>            Assignee: Ryan Blue
>             Fix For: 1.8.0
>
>         Attachments: AVRO-1692.1.patch
>
>
> The initial logical types implementation assumed that there would only be one logical type per concrete class and kept a lookup table from class to conversion. There are cases where this assumption doesn't work. For example, both time-millis and time-micros can be represented by the same class, LocalTime, and the write path should use the correct logical type's conversion depending on the schema.


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