[
https://issues.apache.org/jira/browse/HIVE-28551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887029#comment-17887029
]
Stamatis Zampetakis commented on HIVE-28551:
--------------------------------------------
Hey [~ximz], thanks for the PR. I am checking it. I am also trying to
understand if the write id conflict that affects the query cache is a more
general problem that affects the transactional semantics of ACID tables.
> Stale results when executing queries over recreated transactional tables
> ------------------------------------------------------------------------
>
> Key: HIVE-28551
> URL: https://issues.apache.org/jira/browse/HIVE-28551
> Project: Hive
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: HiveServer2
> Affects Versions: 4.0.1
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Attachments: results_cache_invalidation3.q
>
>
> SQL queries return stale results from the cache when the tables involved in
> the queries are dropped and then recreated with the same name.
> The problem can be reproduced by executing the following sequence of queries.
> {code:sql}
> CREATE TABLE author (fname STRING) STORED AS ORC
> TBLPROPERTIES('transactional'='true');
> INSERT INTO author VALUES ('Victor');
> SELECT fname FROM author;
> DROP TABLE author;
> CREATE TABLE author (fname STRING) STORED AS ORC
> TBLPROPERTIES('transactional'='true');
> INSERT INTO author VALUES ('Alexander');
> SELECT fname FROM author;
> {code}
> The first execution of the SELECT query correctly returns "Victor" as a
> result.
> The second execution of the SELECT query incorrectly returns "Victor" while
> it should return "Alexander".
> The problem manifestates only when the hive.query.results.cache.enabled is
> set to true.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
