You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Lars Volker (JIRA)" <ji...@apache.org> on 2018/02/23 02:22:00 UTC

[jira] [Resolved] (IMPALA-4167) Support insert plan hints for CREATE TABLE AS SELECT

     [ https://issues.apache.org/jira/browse/IMPALA-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Volker resolved IMPALA-4167.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.12.0
                   Impala 3.0

> Support insert plan hints for CREATE TABLE AS SELECT
> ----------------------------------------------------
>
>                 Key: IMPALA-4167
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4167
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Frontend
>    Affects Versions: Impala 2.5.0, Impala 2.4.0, Impala 2.6.0, Impala 2.7.0
>            Reporter: Alexander Behm
>            Assignee: Csaba Ringhofer
>            Priority: Major
>              Labels: ramp-up
>             Fix For: Impala 3.0, Impala 2.12.0
>
>
> In order to tune ETL processes we should also support the same plan hints for CREATE TABLE AS SELECT (CTAS) statements that we already support for INSERT statements. Otherwise, the convenience of a CTAS may be somewhat lost, or the generated data may not be as efficient as it could be with CREATE + INSERT + hints.
> The placement of the hint should be as in Oracle's syntax:
> {code}
> CREATE /*+ clustered  sort(day,hour) */ TABLE t AS
> SELECT * from src;
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)