hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namit Jain (JIRA)" <>
Subject [jira] Commented: (HIVE-1897) Alter command execution "when HDFS is down" results in holding stale data in MetaStore
Date Mon, 24 Jan 2011 17:06:44 GMT


Namit Jain commented on HIVE-1897:

This still does not work if the client dies after making the metadata change.
However, this does reduce the window.


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

> ---------------------------------------------------------------------------------------
>                 Key: HIVE-1897
>                 URL:
>             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 (5).
>            Reporter: Chinna Rao Lalam
>            Assignee: Chinna Rao Lalam
>             Fix For: 0.7.0
>         Attachments: HIVE-1897.1.patch
> 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.

View raw message