hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mithun Radhakrishnan (JIRA)" <>
Subject [jira] [Commented] (HIVE-17747) HMS DropTableMessage should include the full table object
Date Wed, 18 Oct 2017 18:45:01 GMT


Mithun Radhakrishnan commented on HIVE-17747:

I'm regret being late to this party, I truly do.

The code in {{hive/metastore/messaging}} mirrors that in {{hcatalog/messaging}}, which uses
sparse messages. The entire motivation behind keeping the messages devoid of the actual Thrift
object ({{Database}}, {{Table}}, {{Partition}}, {{StorageDescriptor}}) is that they bloat
the size of the message. It is not uncommon for us in production to have >1000 partitions
added in a single {{addPartitions()}} call. {{Partition}} objects tend to possess a lot of
redundant information, causing the message size to become enormous.

It looks like that ship sailed with HIVE-15522. Your solution here is consistent with HIVE-15522,
so it should stand. :/ I'll raise a separate JIRA to deal with sparser messages.

> HMS DropTableMessage should include the full table object
> ---------------------------------------------------------
>                 Key: HIVE-17747
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: HCatalog, Metastore
>    Affects Versions: 2.3.0
>            Reporter: Dan Burkert
>            Assignee: Dan Burkert
>             Fix For: 3.0.0, 2.4.0
>         Attachments: HIVE-17747.0.patch
> I have a notification log follower use-case which requires accessing the parameters of
dropped tables, so it would be useful if the {{DROP_TABLE}} events in the notification log
included the full table object, as the create and alter events do.

This message was sent by Atlassian JIRA

View raw message