[jira] [Commented] (HIVE-20137) Truncate for Transactional tables should use base_x
[ https://issues.apache.org/jira/browse/HIVE-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539482#comment-16539482 ] Eugene Koifman commented on HIVE-20137: --- this https://issues.apache.org/jira/browse/HIVE-19387?focusedCommentId=16539306=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16539306 > Truncate for Transactional tables should use base_x > --- > > Key: HIVE-20137 > URL: https://issues.apache.org/jira/browse/HIVE-20137 > Project: Hive > Issue Type: Improvement > Components: Transactions >Affects Versions: 3.0.0 >Reporter: Eugene Koifman >Priority: Major > > This is a follow up to HIVE-19387. > Once we have a lock that blocks writers but not readers (HIVE-19369), it > would make sense to make truncate create a new base_x, where is x is a > writeId in current txn - the same as Insert Overwrite does. > This would mean it can work w/o interfering with existing writers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-20137) Truncate for Transactional tables should use base_x
[ https://issues.apache.org/jira/browse/HIVE-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539444#comment-16539444 ] Sergey Shelukhin commented on HIVE-20137: - What does it do right now? > Truncate for Transactional tables should use base_x > --- > > Key: HIVE-20137 > URL: https://issues.apache.org/jira/browse/HIVE-20137 > Project: Hive > Issue Type: Improvement > Components: Transactions >Affects Versions: 3.0.0 >Reporter: Eugene Koifman >Priority: Major > > This is a follow up to HIVE-19387. > Once we have a lock that blocks writers but not readers (HIVE-19369), it > would make sense to make truncate create a new base_x, where is x is a > writeId in current txn - the same as Insert Overwrite does. > This would mean it can work w/o interfering with existing writers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
