[jira] [Updated] (IMPALA-3446) Materialized views

["Quanlong Huang (Jira)" <ji...@apache.org>]

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

Quanlong Huang updated IMPALA-3446:
-----------------------------------
    Issue Type: Epic  (was: New Feature)
      Priority: Major  (was: Minor)

Thank [~xqhe]! Assigned this to you. Some items are finished, e.g. IMPALA-10723.

I changed this to an Epic so we can create specific items under this.

> Materialized views
> ------------------
>
>                 Key: IMPALA-3446
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3446
>             Project: IMPALA
>          Issue Type: Epic
>          Components: Frontend
>    Affects Versions: Impala 2.5.0
>            Reporter: Marcell Szabo
>            Assignee: Xianqing He
>            Priority: Major
>
> This JIRA is a placeholder for this big topic.
> Some user stories I can imagine under the epic:
> # materialized view is a CTAS where the SELECT is saved in the HMS and can be rerun by a simple command
> # materialized view detects that the source data has changed and falls back to be a view instead of SELECT *
> # materialized view detects that the source data has changed and reruns the CTAS automatically
> # ... reruns only the necessary changes (e.g. if only some of the partitions change)
> # Impala and Hive to have common semantics of materialized views (https://issues.apache.org/jira/browse/HIVE-10459)
> # materialized view stores extra statistics that help the optimizer, storing the full resultset is optional
> # query optimizer checks for every query whether part of the query plan can be covered by an existing materialized view



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org