You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/02/09 16:26:00 UTC
[jira] [Updated] (HIVE-27328) Acid dirCache is not invalidated in TezAMs while dropping table
[ https://issues.apache.org/jira/browse/HIVE-27328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HIVE-27328:
----------------------------------
Labels: pull-request-available (was: )
> Acid dirCache is not invalidated in TezAMs while dropping table
> ---------------------------------------------------------------
>
> Key: HIVE-27328
> URL: https://issues.apache.org/jira/browse/HIVE-27328
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Labels: pull-request-available
>
> The cache introduced in HIVE-22825 is not invalidated in TezAMs which can eventually lead to query failures if the same table is used in a scenario like below:
> 1. CREATE TABLE
> 2. INSERT OVERWRITE
> 3. SELECT
> 4. DROP TABLE
> ...
> in this case if 2) wrote a file like year=2011/base_0000001/bucket_00000_*1* (task attempt = 1), and in the next iteration it wrote year=2011/base_0000001/bucket_00000_*0* (task attempt = 0), then acid dirCache contains an invalid value within the configured time range *hive.txn.acid.dir.cache.duration*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)