Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Impala 4.1.0
-
None
-
ghx-label-9
Description
If we insert data into an acid partitioned table from Hive, the generated events will be like open_txn -> alter_partition -> commit_txn.
In alter_partition event, we will refresh the partition (without refreshing file metadata) because the write id with the partition object in the event > write id of the cached partition. Then, in commit_txn event, we still do the same write id check. However, the write id is still the same, so we end up don't fresh file metadata.
Attachments
Issue Links
- is caused by
-
IMPALA-10923 Fine grained table refreshing at partition level events for transactional tables
- Resolved