A user can specify “required freshness” of data in a materialized view via
If a query is executed against stale data, its result will be cached by HiveServer2 to avoid re - execution at a later point in time. This cache will now contain stale data. A different query session might not be able to tolerate stale data or have a shorter acceptable time window. Right now, it will receive the query result cache content independent of its own hive.materializedview.rewriting.time.window setting, potentially leading to unexpected results.