[
https://issues.apache.org/jira/browse/HIVE-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846500#comment-16846500
]
Todd Lipcon commented on HIVE-21757:
------------------------------------
[~gopalv] what do you think about allocating a writeID for the compaction, but
not using it in the filename for the base data? This would serve to bump the
table's writeID and change its validWriteIdList, which is what we need to
invalidate the file-listing cache in Impala. Without this, we'll end up getting
query failures after the cleaner has run.
> ACID: use a new write id for compaction's output instead of the visibility id
> -----------------------------------------------------------------------------
>
> Key: HIVE-21757
> URL: https://issues.apache.org/jira/browse/HIVE-21757
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 4.0.0
> Reporter: Vaibhav Gumashta
> Priority: Major
>
> HIVE-20823 added support for running compaction within a transaction. To
> control the visibility of the output directory, it uses
> base_writeId_visibilityId, where visibilityId is the transaction id of the
> transaction that the compactor ran in. Perhaps we can keep using the
> base_writeId format, by allocating a new writeId for the compactor and
> creating the new base/delta with that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
