hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4545) HS2 should return describe table results without space padding
Date Fri, 16 Aug 2013 00:00:55 GMT

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

Thejas M Nair commented on HIVE-4545:
-------------------------------------

[~appodictic] Without this patch, 'describe table' in beeline running against hive server2
returns something like 

{code}
'a                   ','int                 ','None                '
{code}

instead of 

{code}
'a','int',''
{code}

While it might make sense for the hive cli to add space padding and replace empty comments
with None, that is not a good idea for jdbc application. For example a jdbc based gui tool
will take of formatting on its side.
The goal is to be able to get 'raw' data from the familiar DDL commands without any changes
to make it more human readable.


                
> HS2 should return describe table results without space padding
> --------------------------------------------------------------
>
>                 Key: HIVE-4545
>                 URL: https://issues.apache.org/jira/browse/HIVE-4545
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-4545-1.patch, HIVE-4545.2.patch, HIVE-4545.3.patch
>
>
> HIVE-3140 changed behavior of 'DESCRIBE table;' to be like 'DESCRIBE FORMATTED table;'.
HIVE-3140 introduced changes to not print header in 'DESCRIBE table;'. But jdbc/odbc calls
still get fields padded with space for the 'DESCRIBE table;' query.
> As the jdbc/odbc results are not for direct human consumption the space padding should
not be done for hive server2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message