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

Aihua Xu commented on HIVE-14146:
---------------------------------

[~pvary] Yeah. You may need to rebase to the latest change. Do you need to 
generate the new baseline for your new test case?

> Column comments with "\n" character "corrupts" table metadata
> -------------------------------------------------------------
>
>                 Key: HIVE-14146
>                 URL: https://issues.apache.org/jira/browse/HIVE-14146
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 2.2.0
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>         Attachments: HIVE-14146.2.patch, HIVE-14146.3.patch, 
> HIVE-14146.4.patch, HIVE-14146.5.patch, HIVE-14146.6.patch, 
> HIVE-14146.7.patch, HIVE-14146.patch
>
>
> Create a table with the following(noting the \n in the COMMENT):
> {noformat}
> CREATE TABLE commtest(first_nm string COMMENT 'Indicates First name\nof an 
> individual’);
> {noformat}
> Describe shows that now the metadata is messed up:
> {noformat}
> beeline> describe commtest;
> +-------------------+------------+-----------------------+--+
> |     col_name      | data_type  |        comment        |
> +-------------------+------------+-----------------------+--+
> | first_nm             | string       | Indicates First name  |
> | of an individual  | NULL       | NULL                  |
> +-------------------+------------+-----------------------+--+
> {noformat}



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

Reply via email to