hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (HIVE-3680) Include Table information in Hive's AddPartitionEvent.
Date Fri, 16 Nov 2012 02:03:12 GMT


Hudson commented on HIVE-3680:

Integrated in Hive-trunk-h0.21 #1799 (See [])
    HIVE-3680 : Include Table information in Hive's AddPartitionEvent. (Mithun Radhakrishnan
via Ashutosh Chauhan) (Revision 1409861)

     Result = FAILURE
hashutosh :
Files : 
* /hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/
* /hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/events/
* /hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/events/
* /hive/trunk/metastore/src/test/org/apache/hadoop/hive/metastore/

> Include Table information in Hive's AddPartitionEvent.
> ------------------------------------------------------
>                 Key: HIVE-3680
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.9.1
>            Reporter: Mithun Radhakrishnan
>            Assignee: Mithun Radhakrishnan
>             Fix For: 0.10.0
>         Attachments: HIVE-3680.branch9.patch, HIVE-3680.trunk.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:

View raw message