[
https://issues.apache.org/jira/browse/HIVE-24987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355286#comment-17355286
]
Vihang Karajgaonkar commented on HIVE-24987:
--------------------------------------------
Published a PR with the proposed change.
> hive.metastore.disallow.incompatible.col.type.changes is too restrictive for
> some storage formats
> -------------------------------------------------------------------------------------------------
>
> Key: HIVE-24987
> URL: https://issues.apache.org/jira/browse/HIVE-24987
> Project: Hive
> Issue Type: Improvement
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently when {{hive.metastore.disallow.incompatible.col.type.changes}} is
> set to true it disallows any schema changes which are deemed as backwards
> incompatible e.g dropping a column of a table. While this may be a correct
> thing to do for Parquet or Orc tables, it is too restrictive for storage
> formats like Kudu.
> Currently, for Kudu tables, Impala supports dropping a column. But if we set
> this config to true metastore disallows changing the schema of the metastore
> table. I am assuming this would be problematic for Iceberg tables too which
> supports such schema changes.
> The proposal is to have a new configuration which provided a exclusion list
> of the table fileformat where this check will be skipped. Currently, we will
> only include Kudu tables to skip this check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
