[
https://issues.apache.org/jira/browse/HIVE-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-5158:
------------------------------
Attachment: HIVE-5158.D12573.8.patch
sershe updated the revision "HIVE-5158 [jira] allow getting all partitions for
table to also use direct SQL path".
Fix issue with newly-added max support - different subsets are returned by
SQL and ORM, due to lack of order when filtering. I verified some of these
tests, will run all tests later today.
Reviewers: ashutoshc, JIRA
REVISION DETAIL
https://reviews.facebook.net/D12573
CHANGE SINCE LAST DIFF
https://reviews.facebook.net/D12573?vs=39525&id=39585#toc
MANIPHEST TASKS
https://reviews.facebook.net/T63
BRANCH
HIVE-5158
ARCANIST PROJECT
hive
AFFECTED FILES
metastore/src/java/org/apache/hadoop/hive/metastore/MetaStoreDirectSql.java
metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java
metastore/src/test/org/apache/hadoop/hive/metastore/VerifyingObjectStore.java
ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java
ql/src/java/org/apache/hadoop/hive/ql/optimizer/ppr/PartitionPruner.java
To: JIRA, ashutoshc, sershe
> allow getting all partitions for table to also use direct SQL path
> ------------------------------------------------------------------
>
> Key: HIVE-5158
> URL: https://issues.apache.org/jira/browse/HIVE-5158
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-5158.D12573.1.patch, HIVE-5158.D12573.2.patch,
> HIVE-5158.D12573.3.patch, HIVE-5158.D12573.4.patch, HIVE-5158.D12573.5.patch,
> HIVE-5158.D12573.6.patch, HIVE-5158.D12573.7.patch, HIVE-5158.D12573.8.patch
>
>
> While testing some queries I noticed that getPartitions can be very slow
> (which happens e.g. in non-strict mode with no partition column filter); with
> a table with many partitions it can take 10-12s easily. SQL perf path can
> also be used for this path.
--
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: http://www.atlassian.com/software/jira
