[ 
https://issues.apache.org/jira/browse/HIVE-26355?focusedWorklogId=786619&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-786619
 ]

ASF GitHub Bot logged work on HIVE-26355:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Jun/22 14:31
            Start Date: 30/Jun/22 14:31
    Worklog Time Spent: 10m 
      Work Description: pvary commented on PR #3406:
URL: https://github.com/apache/hive/pull/3406#issuecomment-1171295279

   > I have also considered to convert the column names at the top method like 
`alter_table`, but since there are only two methods (`areSameColumns` and 
`arePrefixColumns`) that will take use of the compare of names, so I made the 
conversion in these two methods.
   
   Could you please add a javadoc which describes that the methods are case 
independent?




Issue Time Tracking
-------------------

    Worklog Id:     (was: 786619)
    Time Spent: 50m  (was: 40m)

> Column compare should be case insensitive for name
> --------------------------------------------------
>
>                 Key: HIVE-26355
>                 URL: https://issues.apache.org/jira/browse/HIVE-26355
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 4.0.0-alpha-1
>            Reporter: Wechar
>            Assignee: Wechar
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0-alpha-2
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Hive stores all name related value as lower case, such as db_name, tbl_name, 
> col_name etc. But the compare of {{FieldSchema}} does not ignore the case of 
> name, which may cause incorrect result of compare.
> *Bug Description:*
> Some computing engines are case sensitive for column name. For example, Spark 
> will add a table property to save the column fields when creating a table, 
> and will replace column fields with this property when fetching table fields.
> When calling {{*ALTER TABLE ... ADD COLUMNS*}}, the compare of fields between 
> old table and new table will be not expected, and the ADD COLUMNS operation 
> will be cascaded to PARTITIONS, which is unnecessary and time consuming if 
> the table has many partitions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to