[jira] [Updated] (HIVE-20773) Query result cache might contain stale MV data

["Oliver Draese (JIRA)" <ji...@apache.org>]

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

Oliver Draese updated HIVE-20773:
---------------------------------
    Description: 
A user can specify “required freshness” of data in a materialized view via 

hive.materializedview.rewriting.time.window=<time>

 

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.

> Query result cache might contain stale MV data
> ----------------------------------------------
>
>                 Key: HIVE-20773
>                 URL: https://issues.apache.org/jira/browse/HIVE-20773
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 4.0.0
>            Reporter: Oliver Draese
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Critical
>
> A user can specify “required freshness” of data in a materialized view via 
> hive.materializedview.rewriting.time.window=<time>
>  
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)