[ 
https://issues.apache.org/jira/browse/HIVE-13146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172077#comment-15172077
 ] 

Aihua Xu commented on HIVE-13146:
---------------------------------

Seems we should also handle "ALTER TABLE table_name SET TBLPROPERTIES" case. 
Probably we can do that in org.apache.hadoop.hive.ql.io.orc.CompressionKind 
class to override ValueOf() so we can handle both cases in one place. When it's 
called, we will convert to upper case and throw exception if it's not one of 
the value.

> OrcFile table property values are case sensitive
> ------------------------------------------------
>
>                 Key: HIVE-13146
>                 URL: https://issues.apache.org/jira/browse/HIVE-13146
>             Project: Hive
>          Issue Type: Bug
>          Components: ORC
>    Affects Versions: 1.2.1
>            Reporter: Andrew Sears
>            Assignee: Yongzhi Chen
>            Priority: Minor
>         Attachments: HIVE-13146.1.patch, HIVE-13146.2.patch
>
>
> In Hive v1.2.1.2.3, with Tez , create an external table with compression 
> SNAPPY value marked as lower case.  Table is created successfully.  Insert 
> data into table fails with no enum constant error.
> CREATE EXTERNAL TABLE mydb.mytable 
> (id int)
>   PARTITIONED BY (business_date date)
> STORED AS ORC
> LOCATION
>   '/data/mydb/mytable'
> TBLPROPERTIES (
>   'orc.compress'='snappy');
> set hive.exec.dynamic.partition=true;
> set hive.exec.dynamic.partition.mode=nonstrict;
> INSERT OVERWRITE mydb.mytable PARTITION (business_date)
> SELECT * from mydb.sourcetable;
> Caused by: java.lang.IllegalArgumentException: No enum constant 
> org.apache.hadoop.hive.ql.io.orc.CompressionKind.snappy
>       at java.lang.Enum.valueOf(Enum.java:238)
>       at 
> org.apache.hadoop.hive.ql.io.orc.CompressionKind.valueOf(CompressionKind.java:25)
> Constant SNAPPY needs to be uppercase in definition to fix.  Case should be 
> agnostic or throw error on creation of table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to