[
https://issues.apache.org/jira/browse/HIVE-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752496#comment-13752496
]
Phabricator commented on HIVE-5158:
-----------------------------------
ashutoshc has requested changes to the revision "HIVE-5158 [jira] allow getting
all partitions for table to also use direct SQL path".
Question on supporting max.
INLINE COMMENTS
metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java:1387
Seems like its not hard to support max in this scenario. We can simply do
query.setRange(0, max) for it. Did you consider supporting it?
REVISION DETAIL
https://reviews.facebook.net/D12573
BRANCH
HIVE-5158
ARCANIST PROJECT
hive
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
>
>
> 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
