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

Posted to issues@hive.apache.org by "Denys Kuzmenko (Jira)" <ji...@apache.org> on 2021/04/23 08:35:00 UTC

[jira] [Updated] (HIVE-25050) Disable 'hive.metastore.acid.truncate.usebase' config as it's introducing backward incompatible change

     [ https://issues.apache.org/jira/browse/HIVE-25050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denys Kuzmenko updated HIVE-25050:
----------------------------------
    Description: 
HIVE-20137 introduces new file metadata and writes it into base files during truncate table operations.

If there is an older version of HMS running in the cluster that doesn't contain HIVE-20137 it won't be able to handle the new file metadata and will fail to inspect tables that have been truncated, thereby skipping compacting them.

We should disable 'hive.metastore.acid.truncate.usebase' until we don't have a fix that addresses the backward incompatibility.

> Disable 'hive.metastore.acid.truncate.usebase' config as it's introducing backward incompatible change
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-25050
>                 URL: https://issues.apache.org/jira/browse/HIVE-25050
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Denys Kuzmenko
>            Priority: Major
>
> HIVE-20137 introduces new file metadata and writes it into base files during truncate table operations.
> If there is an older version of HMS running in the cluster that doesn't contain HIVE-20137 it won't be able to handle the new file metadata and will fail to inspect tables that have been truncated, thereby skipping compacting them.
> We should disable 'hive.metastore.acid.truncate.usebase' until we don't have a fix that addresses the backward incompatibility.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)