[
https://issues.apache.org/jira/browse/HIVE-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116835#comment-15116835
]
Wei Zheng commented on HIVE-11716:
----------------------------------
This JIRA solves the problems below:
* Explicitly disallow switching hive.txn.manager (This was not allowed always,
but we didn't throw out error, and SET command gives people impression that
this entry can be changed because it does show the new value, which is
misleading)
* For queries against ACID table with a transaction manager that doesn't
support ACID, we raise errors. This applies to SELECT, INSERT INTO, INSERT
OVERWRITE, UPDATE and DELETE.
> 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: Wei Zheng
> Priority: Critical
> Attachments: HIVE-11716.1.patch
>
>
> 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)
