[ https://issues.apache.org/jira/browse/HIVE-19387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eugene Koifman updated HIVE-19387: ---------------------------------- Resolution: Fixed Fix Version/s: 3.2.0 Status: Resolved (was: Patch Available) committed to branch-3 > Truncate table for Acid tables conflicts with ResultSet cache > ------------------------------------------------------------- > > Key: HIVE-19387 > URL: https://issues.apache.org/jira/browse/HIVE-19387 > Project: Hive > Issue Type: New Feature > Components: Transactions > Reporter: Eugene Koifman > Assignee: Eugene Koifman > Priority: Blocker > Fix For: 3.2.0 > > Attachments: HIVE-19387.01-branch-3.patch, HIVE-19387.01.patch > > > How should this work? Should it work like Insert Overwrite T select * from T > where 1=2? > This should create a new empty base_x/ and thus operate w/o violating > Snapshot Isolation semantics. > This makes sense for specific partition or unpartitioned table. What about > "Truncate T" where T is partitioned? Is the expectation to wipe out all > partition info or to make each partition empty? -- This message was sent by Atlassian JIRA (v7.6.3#76005)