[
https://issues.apache.org/jira/browse/HIVE-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295894#comment-13295894
]
Bhushan Mandhani commented on HIVE-3144:
----------------------------------------
No they don't solve this problem. One of those two patches is anyway
uncommitted.
> 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
> Components: Metastore
> 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