THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
When bootstrap dump is in progress, it blocks rename table/partition operations on any tables of the dumped database and throws HiveException. Once bootstrap dump is completed, rename operations are enabled and will work as normal. If HiveServer2 crashes when bootstrap dump in progress, then rename operations will continue to throw HiveException even after HiveServer2 is restored with no REPL DUMP in progress. This abnormal state should be manually fixed using following work around.
Look up the HiveServer logs for below pair of log messages.
...
REPL LOAD [<dbname>[.<tablename>]] FROM <dirname> [WITH ('key1'='value1', 'key2'='value2')];
This causes a repl dump present in <dirname> (which is to be a fully qualified hdfs url) to be pulled and loaded. If <dbname> is specified, and the original dump was a db-level dump, this allows us to do db-rename-mapping on import. If <dbname>.<tablename> was specified, and the original dump was a table-level dump, then this allows us to do a table-rename-mapping on import. If neither dbname nor tablename are specified, the original dbname and tablename are used, as recorded in the dump. REPL LOAD command have an optional WITH clause to set command specific configurations to be used when try to copy from source cluster. These configurations are only used by the corresponding REPL LOAD command and won't be used for other queries running in the same session.
Return values:
- Error codes returned as normal.
- Does not return anything in ResultSet, expects user to run REPL STATUS to check.
...