Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 27 Jul 2015 22:18:04 +0000 (UTC)
From: "Swarnim Kulkarni (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12845873.1437136642000.301735.1438035484596@Atlassian.JIRA>
In-Reply-To: <JIRA.12845873.1437136642000@Atlassian.JIRA>
References: <JIRA.12845873.1437136642000@Atlassian.JIRA>
 <JIRA.12845873.1437136642445@arcas>
Subject: [jira] [Commented] (HIVE-11288) Avro SerDe InstanceCache returns
 incorrect schema
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Swarnim Kulkarni commented on HIVE-11288:
-----------------------------------------

[~gphillips] I might be overlooking something but shouldn't the equals method be on the InstanceCache instead of TestInstanceCache? Technically would be awesome to have both hashcode and equals on that class if we are using it directly for doing the comparison in containsKey.

> Avro SerDe InstanceCache returns incorrect schema
> -------------------------------------------------
>
>                 Key: HIVE-11288
>                 URL: https://issues.apache.org/jira/browse/HIVE-11288
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Greg Phillips
>            Assignee: Greg Phillips
>         Attachments: HIVE-11288.2.patch, HIVE-11288.3.patch, HIVE-11288.patch
>
>
> To reproduce this error, take two fields in an avro schema document matching the following:
> "type" :  { "type": "array", "items": [ "null",  { "type": "map", "values": [ "null", "string" ] } ]  }
> "type" : { "type": "map", "values": [ "null" , { "type": "array", "items": [ "null" , "string"] } ] }
> After creating two tables in hive with these schemas, the describe statement on each of them will only return the schema for the first one loaded.  This is due to a hashCode() collision in the InstanceCache.  
> A patch will be included in this ticket shortly which removes the hashCode call from the InstanceCache's internal HashMap, and instead provides the entire schema object.


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