You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2017/10/10 00:22:00 UTC

[jira] [Commented] (HIVE-17671) TableScanDesc.isAcidTable is restricted to FullAcid tables

    [ https://issues.apache.org/jira/browse/HIVE-17671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197923#comment-16197923 ] 

Sergey Shelukhin commented on HIVE-17671:
-----------------------------------------

Does it actually cause problems? I'm assuming from Wei's changes that it intends to guard full-acid-specific logic.

> TableScanDesc.isAcidTable is restricted to FullAcid tables
> ----------------------------------------------------------
>
>                 Key: HIVE-17671
>                 URL: https://issues.apache.org/jira/browse/HIVE-17671
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Transactions
>            Reporter: Eugene Koifman
>
>     _isAcidTable = AcidUtils.isAcidTable(this.tableMetadata);_
> is changed to 
>     _isAcidTable = AcidUtils.isFullAcidTable(this.tableMetadata);_
> This property is then checked all over the place - why?
> This then affects TableScanDesc.isAcidTable() so FetchTask, HiveInputFormat etc assume that they are handling Acid read only if it's full acid... this doesn't look right



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)