hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Goodman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-887) Allow SELECT <col> without a mapreduce job
Date Wed, 05 Mar 2014 19:56:43 GMT

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

Tim Goodman commented on HIVE-887:
----------------------------------

Hmm, apparently I have to do:
SET hive.fetch.task.conversion=more;
(default was hive.fetch.task.conversion=minimal)

> Allow SELECT <col> without a mapreduce job
> ------------------------------------------
>
>                 Key: HIVE-887
>                 URL: https://issues.apache.org/jira/browse/HIVE-887
>             Project: Hive
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Eric Sun
>            Assignee: Ning Zhang
>             Fix For: 0.10.0
>
>
> I often find myself needing to take a quick look at a particular column of a Hive table.
> I usually do this by doing a 
> SELECT * from <table> LIMIT 20;
> from the CLI.  Doing this is pretty fast since it doesn't require a mapreduce job.  However,
it's tough to examine just 1 or 2 columns when the table is very wide.
> So, I might do
> SELECT <col> from <table> LIMIT 20;
> but it's much slower since it requires a map-reduce.  It'd be really convenient if a
map-reduce wasn't necessary.
> Currently a good work around is to do
> hive -e "select * from table" | cut --key=n
> but it'd be more convenient if it were built in since it alleviates the need for column
counting.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message