[
https://issues.apache.org/jira/browse/HIVE-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344129#comment-16344129
]
Eugene Koifman edited comment on HIVE-18575 at 1/29/18 10:36 PM:
-----------------------------------------------------------------
hive.acid.table.scan and
TABLE_IS_TRANSACTIONAL = "transactional"; as in
AcidUtils.isTablePropertyTransactional
when set on Configuration were always meant for full acid and only full acid
The code running on the Grid uses these to know it's doing acid
I think is the part that got broken - it's now set where it shouldn't be
was (Author: ekoifman):
hive.acid.table.scan and
TABLE_IS_TRANSACTIONAL = "transactional"; as in
AcidUtils.isTablePropertyTransactional
when set on Configuration were always meant for full acid and only full acid
I think is the part that got broken - it's now set where it shouldn't be
> ACID properties usage in jobconf is ambiguous for MM tables
> -----------------------------------------------------------
>
> Key: HIVE-18575
> URL: https://issues.apache.org/jira/browse/HIVE-18575
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
>
> Vectorization checks for ACID table trigger for MM tables where they don't
> apply. Other places seem to set the setting for transactional case while most
> of the code seems to assume it implies full acid.
> Overall, many places in the code use the settings directly or set the ACID
> flag without setting the ACID properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
