[
https://issues.apache.org/jira/browse/HIVE-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757303#comment-13757303
]
Sergey Shelukhin commented on HIVE-5158:
----------------------------------------
In some test the database wasn't created, so SQL failed with PARTITION table
not found. When it falls back to JDO presumably the db is getting created,
judging by DN info logging.
External (to metastore) tx can be anywhere there code calls beginTransaction on
metastore before doing stuff, for example in many drop-table cases.
External code calls begin, then we call begin, SQL fails and we intend to fall
back and call rollback; this won't allow us to fall back though as the caller
will now fail anyway.
> 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
>
>
> 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
