hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <>
Subject [jira] [Updated] (HIVE-11752) Pre-materializing complex CTE queries
Date Fri, 29 Jan 2016 12:05:40 GMT


Jesus Camacho Rodriguez updated HIVE-11752:
    Attachment: HIVE-11752.03.patch

[~navis], I have continued the work on this patch as we have a lot of interest that it goes

I have rebased it and fix some issues that were pending when materialization was not exercised
(related to the multiple references of the materialization in the query).

I went through the patch and it seems one of the aspects pending (but that we could work on
in a follow-up JIRA case) would be considering for materialization CTEs that are defined within
views. Currently they are ignored.

Thus, I think most of the work was already done and the patch might be ready to go in. [~navis],
was there something additional still missing?

[~jpullokkaran], do you also want to take a look at the patch to confirm that it meets our


> Pre-materializing complex CTE queries
> -------------------------------------
>                 Key: HIVE-11752
>                 URL:
>             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

View raw message