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

David Phillips updated HIVE-178:
--------------------------------

      Priority: Minor  (was: Major)
    Issue Type: Wish  (was: Bug)

Changing from bug to wish as the current behavior is correct.  The current 
workaround is to select from a table with a single row, or select from a small 
table with LIMIT 1.

For simple cases like the example, skipping the Hadoop job entirely would be 
nice.

> SELECT without FROM; dropping unnecessary table references
> ----------------------------------------------------------
>
>                 Key: HIVE-178
>                 URL: https://issues.apache.org/jira/browse/HIVE-178
>             Project: Hadoop Hive
>          Issue Type: Wish
>          Components: Query Processor
>            Reporter: Adam Kramer
>            Priority: Minor
>
> SELECT 1+1;
> should just return '2', but instead hive fails because no table is listed.
> SELECT 1+1 FROM (empty table);
> should also just return '2', but instead hive "succeeds" because there is "no 
> possible output," so it produces no output. This is the reason I filed under 
> "bug" instead of "improvement:" If it does not return '2' hive should fail.
> So, currently we have to run 
> SELECT 1+1 FROM (actual table with data);
> ...which runs a whole mapreduce step to ignore all of the data in the table 
> before spitting out '2'. This will be exceptionally frustrating if hadoop 
> makes us wait for mapper(s).
> It would be nice to be able to SELECT without specifying a table, and perhaps 
> relatedly, to be able to edit the above query (which worked) to not need to 
> actually process (actual table with data) given that no data is being pulled 
> from it (as we see from the SELECT statement, that table's name or alias does 
> not appear).

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

Reply via email to