Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <711836086.2351265049379945.JavaMail.jira@brutus.apache.org>
Date: Mon, 1 Feb 2010 18:36:19 +0000 (UTC)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Commented: (AVRO-389) ResolvingDecoder does not resolve enum
 well
In-Reply-To: <768815475.159721264957174544.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-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828214#action_12828214 ] 

Doug Cutting commented on AVRO-389:
-----------------------------------

+1  Thanks!

> ResolvingDecoder does not resolve enum well
> -------------------------------------------
>
>                 Key: AVRO-389
>                 URL: https://issues.apache.org/jira/browse/AVRO-389
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>            Reporter: Thiruvalluvan M. G.
>            Assignee: Thiruvalluvan M. G.
>         Attachments: AVRO-389-test.patch, AVRO-389.patch
>
>
> Silly bug. mkEnumAdjust() and its caller don't agree on the order of the arguments. Strange that the bug existed for so long. The test-patch has some new tests to test untested portions of ResolvingEncoder. The actual patch fixes the problem.

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