[
https://issues.apache.org/jira/browse/HIVE-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133287#comment-15133287
]
Wei Zheng commented on HIVE-12064:
----------------------------------
[~ekoifman] Correct me if I'm wrong. In general we want to fail the following
scenarios:
1. CREATE TABLE (with no bucketing or no ORC format) TBLPROPERTIES
("transactional"="true");
Bad news, we currently don't prevent that.
2. ALTER TABLE
2.1 No tblproperties -> "transactional"="false" (Do we allow this? Although no
such need to do that to non-ACID table)
2.2 No tblproperties -> "transactional"="true" (need to check bucketing and
ORC, if not satisfied, fail)
2.3 "transactional"="false" -> "true" (need to check bucketing and ORC, if not
satisfied, fail)
2.4 "transactional"="true" -> "false" (cannot go back)
> prevent transactional=false
> ---------------------------
>
> Key: HIVE-12064
> URL: https://issues.apache.org/jira/browse/HIVE-12064
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 1.0.0
> Reporter: Eugene Koifman
> Assignee: Wei Zheng
> Priority: Critical
> Attachments: HIVE-12064.2.patch, HIVE-12064.patch
>
>
> currently a tblproperty transactional=true must be set to make a table behave
> in ACID compliant way.
> This is misleading in that it seems like changing it to transactional=false
> makes the table non-acid but on disk layout of acid table is different than
> plain tables. So changing this property may cause wrong data to be returned.
> Should prevent transactional=false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
