[
https://issues.apache.org/jira/browse/HIVE-22158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961073#comment-16961073
]
Gabor Kaszab commented on HIVE-22158:
-------------------------------------
Hey [~ngangam],
We have recently made an upgrade on Impala to pull in the latest Hive build and
we observe that due to this change Impala is no longer available to upgrade a
non-ACID table to become an ACID table. Is it intentional from Hive side to do
this restriction? If yes, then could you help me understand the motivation
behind?
Cheers,
Gabor
> HMS Translation layer - Disallow non-ACID MANAGED tables.
> ---------------------------------------------------------
>
> Key: HIVE-22158
> URL: https://issues.apache.org/jira/browse/HIVE-22158
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
> Affects Versions: 4.0.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22158.1.patch, HIVE-22158.1.patch,
> HIVE-22158.2.patch
>
>
> In the recent commits, we have allowed non-ACID MANAGED tables to be created
> by clients that have some form of ACID WRITE capabilities.
> I think it would make sense to disallow this entirely. MANAGED tables should
> be ACID tables only.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
