You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2016/01/07 20:50:40 UTC
[jira] [Updated] (HIVE-11716) Reading ACID table from non-acid
session should raise an error
[ https://issues.apache.org/jira/browse/HIVE-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eugene Koifman updated HIVE-11716:
----------------------------------
Description:
if someone performs a delete using DbTxnManager and than starts a new session with DummyTxnManager, then previously successfully deleted data will show up.
Once the logic to identify all acid tables being read is there, make sure that
Driver.recordValidTxns() called iff there ACID tables in the query.
We should also not allow writing to ACID table from non-acid session
was:
if someone performs a delete using DbTxnManager and than starts a new session with DummyTxnManager, then previously successfully deleted data will show up.
Once the logic to identify all acid tables being read is there, make sure that
Driver.recordValidTxns() called iff there ACID tables in the query.
> Reading ACID table from non-acid session should raise an error
> --------------------------------------------------------------
>
> Key: HIVE-11716
> URL: https://issues.apache.org/jira/browse/HIVE-11716
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 1.0.0
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Priority: Critical
>
> if someone performs a delete using DbTxnManager and than starts a new session with DummyTxnManager, then previously successfully deleted data will show up.
> Once the logic to identify all acid tables being read is there, make sure that
> Driver.recordValidTxns() called iff there ACID tables in the query.
> We should also not allow writing to ACID table from non-acid session
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)