You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Venky Iyer (JIRA)" <ji...@apache.org> on 2009/03/20 03:53:50 UTC

[jira] Updated: (HIVE-355) print column:value format in hive cli "select * limit k"

     [ https://issues.apache.org/jira/browse/HIVE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Venky Iyer updated HIVE-355:
----------------------------

    Description: 
> select ...... \G

metric: wallpost_volume
   day: 2009-03-17
 value: 9.31625e+07

For tables with a lot of columns, it's very difficult to actually match up column to value. MySQL supports a \G terminator that causes it to print in a colname: value format which is very nice for this sort of thing. 

  was:
> select ...... \G

*************************** 269. row ***************************
metric: wallpost_volume
   day: 2009-03-17
 value: 9.31625e+07

For tables with a lot of columns, it's very difficult to actually match up column to value. MySQL supports a \G terminator that causes it to print in a colname: value format which is very nice for this sort of thing. 


> print column:value format in hive cli "select * limit k"
> --------------------------------------------------------
>
>                 Key: HIVE-355
>                 URL: https://issues.apache.org/jira/browse/HIVE-355
>             Project: Hadoop Hive
>          Issue Type: Improvement
>            Reporter: Venky Iyer
>
> > select ...... \G
> metric: wallpost_volume
>    day: 2009-03-17
>  value: 9.31625e+07
> For tables with a lot of columns, it's very difficult to actually match up column to value. MySQL supports a \G terminator that causes it to print in a colname: value format which is very nice for this sort of thing. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.