[jira] [Commented] (IMPALA-3446) Materialized views
[ https://issues.apache.org/jira/browse/IMPALA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543927#comment-17543927 ] Jian Zhang commented on IMPALA-3446: looking forward to it! [~xqhe] could you share some information about your working status on this feature? > Materialized views > -- > > Key: IMPALA-3446 > URL: https://issues.apache.org/jira/browse/IMPALA-3446 > Project: IMPALA > Issue Type: New Feature > Components: Frontend >Affects Versions: Impala 2.5.0 >Reporter: Marcell Szabo >Priority: Minor > > 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-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-3446) Materialized views
[ https://issues.apache.org/jira/browse/IMPALA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543890#comment-17543890 ] Xianqing He commented on IMPALA-3446: - We are working on it. Can assign it to me? > Materialized views > -- > > Key: IMPALA-3446 > URL: https://issues.apache.org/jira/browse/IMPALA-3446 > Project: IMPALA > Issue Type: New Feature > Components: Frontend >Affects Versions: Impala 2.5.0 >Reporter: Marcell Szabo >Priority: Minor > > 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-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-3446) Materialized views
[ https://issues.apache.org/jira/browse/IMPALA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665602#comment-16665602 ] Ruslan Dautkhanov commented on IMPALA-3446: --- Any updates on this case? Both HIVE-14484 and HIVE-14249 are resolved in Hive so technically materialized views are supported in upstream Hive now. Would be great to have same in Impala, as Impala's use cases are exactly around faster interactive response time, than for Hive. Thank you. > Materialized views > -- > > Key: IMPALA-3446 > URL: https://issues.apache.org/jira/browse/IMPALA-3446 > Project: IMPALA > Issue Type: New Feature > Components: Frontend >Affects Versions: Impala 2.5.0 >Reporter: Marcell Szabo >Priority: Minor > > 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 (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-3446) Materialized views
[ https://issues.apache.org/jira/browse/IMPALA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498527#comment-16498527 ] Ruslan Dautkhanov commented on IMPALA-3446: --- Would also be great to implement MATERIALIZE hint as in Oracle too. [https://oracle-base.com/articles/misc/with-clause#materialize-hint] Basically in Oracle we could run WITH subqueries that will be persisted for the duration of the query, so if that subquery is used multiple times in outer query, a heavy join or any other operation has to run only once. > Materialized views > -- > > Key: IMPALA-3446 > URL: https://issues.apache.org/jira/browse/IMPALA-3446 > Project: IMPALA > Issue Type: New Feature > Components: Frontend >Affects Versions: Impala 2.5.0 >Reporter: Marcell Szabo >Priority: Minor > > 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 (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
