hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remus Rusanu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-5771) Constant propagation optimizer for Hive
Date Mon, 19 May 2014 02:38:39 GMT

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

Remus Rusanu commented on HIVE-5771:
------------------------------------

I'm looking at the Parquet failure. Looks like the first row returned by parquet reader has
a different number of fields than expected. Truth is that the building of the vectorizatized
batch based on the first Parquet returned object was a hack to work around HIVE-6414. Now
that it's fixed, perhaps I should also fix the hack and properly build the factorized batch
out of the object inspectors, not out of the first row. 

> Constant propagation optimizer for Hive
> ---------------------------------------
>
>                 Key: HIVE-5771
>                 URL: https://issues.apache.org/jira/browse/HIVE-5771
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Ted Xu
>            Assignee: Ted Xu
>         Attachments: HIVE-5771.1.patch, HIVE-5771.10.patch, HIVE-5771.2.patch, HIVE-5771.3.patch,
HIVE-5771.4.patch, HIVE-5771.5.patch, HIVE-5771.6.patch, HIVE-5771.7.patch, HIVE-5771.8.patch,
HIVE-5771.9.patch, HIVE-5771.patch, HIVE-5771.patch.javaonly
>
>
> Currently there is no constant folding/propagation optimizer, all expressions are evaluated
at runtime. 
> HIVE-2470 did a great job on evaluating constants on UDF initializing phase, however,
it is still a runtime evaluation and it doesn't propagate constants from a subquery to outside.
> It may reduce I/O and accelerate process if we introduce such an optimizer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message