hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Hagleitner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10175) PartitionPruning lacks a fast-path exit for large IN() queries
Date Thu, 02 Apr 2015 22:19:54 GMT

    [ https://issues.apache.org/jira/browse/HIVE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393580#comment-14393580
] 

Gunther Hagleitner commented on HIVE-10175:
-------------------------------------------

Checking the PartitionPruner - it seems we already have a fast path for "prune()." If you
have more details about where the time is spent this would help.

> PartitionPruning lacks a fast-path exit for large IN() queries
> --------------------------------------------------------------
>
>                 Key: HIVE-10175
>                 URL: https://issues.apache.org/jira/browse/HIVE-10175
>             Project: Hive
>          Issue Type: Bug
>          Components: Physical Optimizer, Tez
>    Affects Versions: 1.2.0
>            Reporter: Gopal V
>            Assignee: Gunther Hagleitner
>            Priority: Minor
>
> TezCompiler::runDynamicPartitionPruning() & ppr.PartitionPruner() calls the graph
walker even if all tables provided to the optimizer are unpartitioned (or temporary) tables.
> This makes it extremely slow as it will walk & inspect a large/complex FilterOperator
later in the pipeline.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message