Metastore is caching too aggressively
-------------------------------------
Key: HIVE-2758
URL: https://issues.apache.org/jira/browse/HIVE-2758
Project: Hive
Issue Type: Bug
Reporter: Kevin Wilfong
Assignee: Kevin Wilfong
The metastore is caching values, like table names and locations too
aggressively, leading to inconsistencies across Hive clients and metastore
Thrift servers.
For example, open two Hive clients, in each call
DESCRIBE FORMATTED table_foo;
Then in one of those clients, execute
ALTER TABLE table_foo RENAME TO table_bar;
Then in both clients call
DESCRIBE FORMATTED table_bar;
In the client that executed the alter command, the location is correct,
however, in the other Hive client, it will still show the original location of
table_foo.
A similar experiment can be done using metastore Thrift servers, substituting
get_table for DESCRIBE FORMATTED and alter_table for ALTER TABLE ... RENAME TO.
On the Thrift server you can see that the one which did not execute the alter
command, not only returns the wrong location, despite calling
get_table('table_bar') it will return a table that still has the name table_foo.
--
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
