[
https://issues.apache.org/jira/browse/HIVE-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841888#comment-13841888
]
Ashutosh Chauhan commented on HIVE-5951:
----------------------------------------
Does this handle the case of insert query which dynamically creates partition
and load partitions in metastore at the end of MR job. That code-path is in
MoveTask::execute() -> Hive.loadDynamicPartitions() ? That path is likely to be
more relevant for this problem instead of from a ddl command someone trying to
add 100s of partitions?
> improve performance of adding partitions from client
> ----------------------------------------------------
>
> Key: HIVE-5951
> URL: https://issues.apache.org/jira/browse/HIVE-5951
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-5951.01.patch, HIVE-5951.nogen.patch,
> HIVE-5951.nogen.patch, HIVE-5951.patch
>
>
> Adding partitions to metastore is currently very inefficient. There are small
> things like, for !ifNotExists case, DDLSemanticAnalyzer gets the full
> partition object for every spec (which is a network call to metastore), and
> then discards it instantly; there's also general problem that too much
> processing is done on client side. DDLSA should analyze the query and make
> one call to metastore (or maybe a set of batched calls if there are too many
> partitions in the command), metastore should then figure out stuff and insert
> in batch.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
