Alter command execution "when HDFS is down" results in holding stale data in 
MetaStore 
---------------------------------------------------------------------------------------

                 Key: HIVE-1897
                 URL: https://issues.apache.org/jira/browse/HIVE-1897
             Project: Hive
          Issue Type: Bug
          Components: Metastore
    Affects Versions: 0.6.0
         Environment: Hadoop 0.20.1, Hive0.6.0 and SUSE Linux Enterprise Server 
10 SP2 (i586) - Kernel 2.6.16.60-0.21-smp (5).
            Reporter: Chinna Rao Lalam


Lets  consider, the  *"DFS"* is down , 

And on executing an alter query say  *"alter table firsttable rename to 
secondtable"*.  
the query execution fails with the following exception:
{color:red} 
InvalidOperationException(message:Unable to access old location 
hdfs://localhost:9000/user/hive/warehouse/firsttable for table 
default.firsttable)
{color}

Now after starting the *DFS* and then executing the same query , the client 
gets the following exception:
{color:red}
NoSuchObjectException(message:default.firsttable table not found)
{color}

h4.Root Cause
In Alter Query execution flow, first *"MetaStore"* operation is executed 
successfully and then *"DFS"* operation is started. In this scenario, *"DFS"* 
is down. As a result, execution of the query failed and partial information of 
the operation is saved.

-- 
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