Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 7 Nov 2012 00:32:12 +0000 (UTC)
From: "Mithun Radhakrishnan (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <995327293.77979.1352248332449.JavaMail.jiratomcat@arcas>
In-Reply-To: <1746122939.77978.1352248212595.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HIVE-3680) Include Table information in Hive's
 AddPartitionEvent.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mithun Radhakrishnan updated HIVE-3680:
---------------------------------------

    Attachment: HIVE-3680.patch

Proposed change.
                
> Include Table information in Hive's AddPartitionEvent.
> ------------------------------------------------------
>
>                 Key: HIVE-3680
>                 URL: https://issues.apache.org/jira/browse/HIVE-3680
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.9.1
>            Reporter: Mithun Radhakrishnan
>             Fix For: 0.9.1
>
>         Attachments: HIVE-3680.patch
>
>
> This has to do with a minor overhaul of the HCatalog notifications that we're attempting in HCATALOG-546.
> It is proposed that HCatalog's notifications (on Add/Drop of Partitions) provide details to identify the affected partitions. 
> Using the Partition object in AddPartitionEvent, one is able to retrieve the values of the partition-keys and the name of the Table. However, the partition-keys themselves aren't available (since the Table instance isn't part of the AddPartitionEvent).
> Adding the table-reference to the AddPartitionEvent and DropPartitionEvent classes will expose all the info we need. (The alternative is to query the metastore for the table's schema and use the partition-keys from there. :/)
> I'll post a patch for this shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira