[
https://issues.apache.org/jira/browse/HIVE-15374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727678#comment-15727678
]
Naveen Gangam commented on HIVE-15374:
--------------------------------------
Thanks Chaoyu. That's basically the fix in the patch. It adds this serde to the
list by default.
I think the right way to fix this is to makes serde's implement a separate
[marker?] interface if they are meant to be stored in the HMS metastore or the
other way around. This is not a good design that hive provides interfaces to
provide custom serde's but these do not work the same way as others because of
this list that no one probably knows about. Perhaps we could refactor this in
the future to make it flexible.
> Hive column comments disappearing/being replaced by "from deserializer"
> -----------------------------------------------------------------------
>
> Key: HIVE-15374
> URL: https://issues.apache.org/jira/browse/HIVE-15374
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 2.0.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Attachments: HIVE-15374.patch
>
>
> After creating a table in hive with column comments, running show create
> table or describe [formatted], on the same table gives "from deserializer"
> instead of the original comments.
> CREATE TABLE `test`(
> `stringid` string COMMENT 'string id',
> `value` string COMMENT 'description')
> ROW FORMAT SERDE
> 'org.apache.hadoop.hive.contrib.serde2.RegexSerDe'
> WITH SERDEPROPERTIES (
> 'input.regex'='(.{1})');
> The comments appear to be stored correctly in the HMS backend DB. Just the
> fetching of this metadata seems to be incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
