Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Follow up jira for HIVE-7723. Explain plan for complex query with lots of partitions is slow due to in-efficient collection used to find a matching ReadEntity.
As part of HIVE-7723, we will create a map during PlanUtils.addPartitionInputs(), we should start with a map if possible in ParseContext::semanticInputs to save CPU burn on this additional operation.
Attachments
Issue Links
- relates to
-
HIVE-7723 Explain plan for complex query with lots of partitions is slow due to in-efficient collection used to find a matching ReadEntity
- Closed