[
https://issues.apache.org/jira/browse/HIVE-15061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609006#comment-15609006
]
Chaoyu Tang commented on HIVE-15061:
------------------------------------
In Hive alter table, both column name and type in the newTable object have been
converted to lower case before it is passed to HMS APIs, therefore there won't
be the case sensitive issues as seen in Impala. Impala might do the same way as
Hive to work around this issue (which seems Impala is doing), or we might seek
a way to validate column names/types and do the case conversion in HMS alter
table.
> Metastore types are sometimes case sensitive
> --------------------------------------------
>
> Key: HIVE-15061
> URL: https://issues.apache.org/jira/browse/HIVE-15061
> Project: Hive
> Issue Type: Bug
> Components: API
> Affects Versions: 1.1.0
> Reporter: Thomas Tauber-Marshall
> Assignee: Chaoyu Tang
>
> Impala recently encountered an issue with the metastore
> ([IMPALA-4260|https://issues.cloudera.org/browse/IMPALA-4260] ) where column
> stats would get dropped when adding a column to a table.
> The reason seems to be that Hive does a case sensitive check on the column
> stats types during an "alter table" and expects the types to be all lower
> case. This case sensitive check doesn't appear to happen when the stats are
> set in the first place.
> We're solving this on the Impala end by storing types in the metastore as all
> lower case, but Hive's behavior here is very confusing. It should either
> always be case sensitive, so that you can't create column stats with types
> that Hive considers invalid, or it should never be case sensitive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
