Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 15 Jun 2012 19:39:43 +0000 (UTC)
From: "Bhushan Mandhani (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <1999561011.19884.1339789183141.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (HIVE-3144) Custom Deserializers Should be Used
 for Thrift Table Objects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bhushan Mandhani created HIVE-3144:
--------------------------------------

             Summary: Custom Deserializers Should be Used for Thrift Table Objects
                 Key: HIVE-3144
                 URL: https://issues.apache.org/jira/browse/HIVE-3144
             Project: Hive
          Issue Type: Bug
            Reporter: Bhushan Mandhani
            Assignee: Bhushan Mandhani
            Priority: Minor


Some tables have custom deserializers. When constructing the column set for these, the deserializer class should be used instead of just reading from the MetaStore. This is already happening when constructing the Table object in package org/apache/hadoop/hive/ql/metadata. However, Thrift API is returning incorrect results for these. We want to move this logic out of this Table object and lower into the stack to fix this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira