You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Marc Limotte (JIRA)" <ji...@apache.org> on 2013/02/01 17:54:12 UTC
[jira] [Created] (HIVE-3973) Misleading error message for DROP
TABLE IF EXISTS when derby is in read-only mode
Marc Limotte created HIVE-3973:
----------------------------------
Summary: Misleading error message for DROP TABLE IF EXISTS when derby is in read-only mode
Key: HIVE-3973
URL: https://issues.apache.org/jira/browse/HIVE-3973
Project: Hive
Issue Type: Bug
Affects Versions: 0.9.0
Reporter: Marc Limotte
Mis-leading error message implies that hive does not respect the IF EXISTS clause for DROP TABLE.
Here's what it looks like from the hive shell:
hive> DROP TABLE IF EXISTS ashgafjhg;
FAILED: Error in semantic analysis: Table not found ashgafjhg
Doesn't matter what the table name is.
Turns out the real issue was that the Derby metastore was already in use. Other commands were throwing this error:
A read-only user or a user in a read-only database...
DROP TABLE should show the error about the read-only user, which is more helpful than the misleading error about "Table not found".
--
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