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

Pedro commented on HIVE-20721:
------------------------------

Hi [~xuefuz]:

First of all thanks for your response.

Yes, I've tried desc table too, the result is the same:

 

> desc table_name
  
||col_name||data_type||comment||
|some_column1|bigint|from deserializer|
|some_column2|string|from deserializer|
|some_column3|string|from deserializer|
|...|...|...|

 

If I use _desc extended table_name_, in "Detailed Table Information" I see the 
json with the correct comments, but the comments in the rows with the table 
columns name only show "from deserializer", as it does with _desc table_name_.

> Describe table sometimes shows "from deserializer" for column comments
> ----------------------------------------------------------------------
>
>                 Key: HIVE-20721
>                 URL: https://issues.apache.org/jira/browse/HIVE-20721
>             Project: Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>    Affects Versions: 1.1.0
>            Reporter: Pedro
>            Priority: Major
>
> When we want to see the comments made in the hive tables, it only shows "from 
> deserializer"
>  
> For example
> > show create table table_name
> CREATE EXTERNAL TABLE `table_name`(
>  `some_column1` bigint COMMENT 'from deserializer', 
>  `some_column2` string COMMENT 'from deserializer', 
>  `some_column3` string COMMENT 'from deserializer',
> [...]
> PARTITIONED BY ( 
>  `dt` string)
> ROW FORMAT SERDE 
>  'org.apache.hive.hcatalog.data.JsonSerDe' 
> STORED AS INPUTFORMAT 
>  'org.apache.hadoop.mapred.TextInputFormat' 
> OUTPUTFORMAT 
>  'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat'
> LOCATION
>  'hdfs://location/table_name'
> TBLPROPERTIES (
>  'json.schema.url'='/location/json/table_name.json', 
>  'transient_lastDdlTime'='1525858710')
>  
> I saw it was resolved in HIVE-6681 but the fixed version was 0.13.0. I'm on 
> 1.1.0 and apparently I have the same issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to