hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shinichi Yamashita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-3993) After upgrading postgres metastore from 0.7.0 to 0.8.0, unable to drop legacy tables or partitions created prior to v0.8.0 upgrade
Date Sat, 16 May 2015 05:50:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shinichi Yamashita updated HIVE-3993:
-------------------------------------
    Affects Version/s: 1.2.0

> After upgrading postgres metastore from 0.7.0 to 0.8.0, unable to drop legacy tables
or partitions created prior to v0.8.0 upgrade
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3993
>                 URL: https://issues.apache.org/jira/browse/HIVE-3993
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.8.0, 0.9.0, 1.2.0
>         Environment: Using Postgres as backend 
>            Reporter: Rick Weber
>            Assignee: Shinichi Yamashita
>         Attachments: HIVE-3993.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When using Postgres as a backend DB I upgraded my metastore from the 0.7.0 schema to
0.8.0.  Afterwhich, I attempted to drop partitions in pre-existing tables and received a very
generic error indicating there was an issue with the metastore.
> After starting the CLI with 
> hive -hiveconf hive.root.logger=DEBUG,console
> And issuing the same drop partition command, I found that the command was failing due
to a constraint violation by COLUMNS_OLD.
> I found an existing Jira that seems to address a similar issue for MySQL
> HIVE-2568
> Opening this Jira so that a similar fix can be applied for the Postgres backend.
> Manually running 
> alter table "COLUMNS_OLD" drop constraint "COLUMNS_SD_ID_fkey";
> on my metastore backend fixed the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message