[
https://issues.apache.org/jira/browse/HCATALOG-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Gates resolved HCATALOG-360.
---------------------------------
Resolution: Invalid
This matches what Hive does. We're working to remove all discrepancies between
Hive DDL and HCat DDL.
> describe on a non existing table should throw an exception
> ----------------------------------------------------------
>
> Key: HCATALOG-360
> URL: https://issues.apache.org/jira/browse/HCATALOG-360
> Project: HCatalog
> Issue Type: Bug
> Components: client
> Affects Versions: 0.4
> Reporter: David Capwell
>
> In 0.2 if you did a describe table against a non existing table then an error
> would be in the log and the return code was 9. In 0.4 the output looks like
> this:
> $ ./bin/hcat -e "describe non_existing_table"
> Warning: $HADOOP_HOME is deprecated.
> WARNING: org.apache.hadoop.metrics.jvm.EventCounter is deprecated. Please use
> org.apache.hadoop.log.metrics.EventCounter in all the log4j.properties files.
> Hive history
> file=/tmp/dcapwell/hive_job_log_dcapwell_201204032317_1700443885.txt
> OK
> Table non_existing_table does not exist
> Time taken: 2.35 seconds
> $ echo $?
> 0
> The return code should indicate that this was an error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
