hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-14498) Freshness period for query rewriting using materialized views
Date Tue, 09 Aug 2016 18:42:20 GMT

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

Jesus Camacho Rodriguez updated HIVE-14498:
-------------------------------------------
    Summary: Freshness period for query rewriting using materialized views  (was: Timeout
for query rewriting using materialized views)

> Freshness period for query rewriting using materialized views
> -------------------------------------------------------------
>
>                 Key: HIVE-14498
>                 URL: https://issues.apache.org/jira/browse/HIVE-14498
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Materialized views
>    Affects Versions: 2.2.0
>            Reporter: Jesus Camacho Rodriguez
>
> Once we have query rewriting in place (HIVE-14496), one of the main issues is data freshness
in the materialized views.
> Since we will not support view maintenance at first, we could include a HiveConf property
to configure a max freshness period (_n timeunits_). If a query comes, and the materialized
view has been populated (by create, refresh, etc.) for a longer period than _n_, then we should
not use it for rewriting the query.
> Optionally, we could print a warning for the user indicating that the materialized was
not used because it was not fresh.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message