You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Carl Steinbach (JIRA)" <ji...@apache.org> on 2011/02/04 21:19:30 UTC
[jira] Updated: (HIVE-1925) insert overwrite in a archived
partition has some issues
[ https://issues.apache.org/jira/browse/HIVE-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1925:
---------------------------------
Priority: Critical (was: Blocker)
Downgrading to critical.
> insert overwrite in a archived partition has some issues
> --------------------------------------------------------
>
> Key: HIVE-1925
> URL: https://issues.apache.org/jira/browse/HIVE-1925
> Project: Hive
> Issue Type: Bug
> Reporter: Namit Jain
> Assignee: Paul Yang
> Priority: Critical
> Fix For: 0.7.0
>
>
> I havent tried a test case, but I ran into the following in some production scanario.
> Table A, partition P is archived - the data is in dfs1
> Then the table's default location changes to another dfs: dfs2
> If I issue the following query:
> insert overwrite table T partition (P)
> select * from T partition P;
> it leaves in the following state:
> A@P output is not archived
> The metadata says it is still archived
> The original location in the metadata still points to the old metadata.
> The old location in dfs1 is not deleted.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira