You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2016/01/29 13:08:39 UTC
[jira] [Commented] (HIVE-11752) Pre-materializing complex CTE
queries
[ https://issues.apache.org/jira/browse/HIVE-11752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123404#comment-15123404 ]
Jesus Camacho Rodriguez commented on HIVE-11752:
------------------------------------------------
I have created uploaded the patch to RB for review: https://reviews.apache.org/r/42960/
> Pre-materializing complex CTE queries
> -------------------------------------
>
> Key: HIVE-11752
> URL: https://issues.apache.org/jira/browse/HIVE-11752
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: HIVE-11752.03.patch, HIVE-11752.1.patch.txt, HIVE-11752.2.patch.txt
>
>
> Currently, hive regards CTE clauses as a simple alias to the query block, which makes redundant works if it's used multiple times in a query. This introduces a reference threshold for pre-materializing the CTE clause as a volatile table (which is not exists in any form of metastore and just accessible from QB).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)