sourabh912 opened a new pull request #2868:
URL: https://github.com/apache/hive/pull/2868
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
2. Ensure that you have created an issue on the Hive project JIRA:
https://issues.apache.org/jira/projects/HIVE/summary
3. Ensure you have added or run the appropriate tests for your PR:
4. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP]HIVE-XXXXX: Your PR title ...'.
5. Be sure to keep the PR description updated to reflect all changes.
6. Please write your PR title to summarize what this PR proposes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
HIVE-20661 added an improvement in loadDynamicPartitions() api in Hive.java
to not add partitions one
by one in HMS. It used to fetch all the existing partitions for a table from
HMS and compare that with
dynamic partitions list to decide old and new partitions to be added to HMS
(in batches). The call to
fetch all partitions has introduced a performance regression for tables with
large number of
partitions (of the order of 100K).
This is fixed for external tables in HIVE-25178. However for ACID tables
there is an open Jira HIVE-25187.
Until we have an appropriate fix in HIVE-25187,we can skip fetching all
partitions. Instead, in the
threadPool which loads each partition individually,call getPartition() to
check if the partition already
exists in HMS or not. This will introduce additional getPartition() call for
every partition to be loaded
dynamically but does not fetch all existing partitions for a table anymore.
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
Since it is an improvement in existing logic, therefore relying on existing
tests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
