[
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mithun Radhakrishnan updated HIVE-3938:
---------------------------------------
Attachment: HIVE-3938.patch
Renamed for running regressions.
[~ashutoshc], you're right, we should discuss moving this kind of thing out of
the transaction, now that you mention it. A failure to notify doesn't imply
that the partition couldn't be added. Client code needs to handle the case that
notifications weren't delivered, anyway.
> Hive MetaStore should send a single AddPartitionEvent for atomically added
> partition-set.
> -----------------------------------------------------------------------------------------
>
> Key: HIVE-3938
> URL: https://issues.apache.org/jira/browse/HIVE-3938
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.10.0, 0.11.0, 0.12.0
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Attachments: HIVE-3938.patch,
> Hive-3938-Support_for_Multi-table-insert.patch
>
>
> HiveMetaStore::add_partitions() currently adds all partitions specified in
> one call using a single meta-store transaction. This acts correctly. However,
> there's one AddPartitionEvent created per partition specified.
> Ideally, the set of partitions added atomically can be communicated using a
> single AddPartitionEvent, such that they are consumed together.
> I'll post a patch that does this.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
