[ https://issues.apache.org/jira/browse/HIVE-24987?focusedWorklogId=607364&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-607364 ]
ASF GitHub Bot logged work on HIVE-24987: ----------------------------------------- Author: ASF GitHub Bot Created on: 04/Jun/21 22:23 Start Date: 04/Jun/21 22:23 Worklog Time Spent: 10m Work Description: vihangk1 commented on pull request #2336: URL: https://github.com/apache/hive/pull/2336#issuecomment-855046128 Thanks @yongzhi for the review. Merged into master. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 607364) Time Spent: 50m (was: 40m) > 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: 50m > 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)