Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.2.0
Description
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.
Attachments
Attachments
Issue Links
- blocks
-
HIVE-18259 Automatic cleanup of invalidation cache for materialized views
- Closed
-
HIVE-18386 Create dummy materialized views registry and make it configurable
- Closed
-
HIVE-18260 Add test case scenarios for materialized views invalidation cache and registry
- Closed
- links to