[
https://issues.apache.org/jira/browse/HIVE-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286322#comment-16286322
]
Jesus Camacho Rodriguez commented on HIVE-14498:
------------------------------------------------
[~ekoifman], makes sense, I will change that. I have added you to the RB link
in case you want to add more feedback, I meant to do it but I forgot when I
created it. Thanks
> 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
> Assignee: Jesus Camacho Rodriguez
> Attachments: HIVE-14498.patch
>
>
> 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.4.14#64029)
