[ 
https://issues.apache.org/jira/browse/HIVE-10362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Coppage updated HIVE-10362:
---------------------------------
    Status: Open  (was: Patch Available)

> Support Type check/conversion in dynamic partition column
> ---------------------------------------------------------
>
>                 Key: HIVE-10362
>                 URL: https://issues.apache.org/jira/browse/HIVE-10362
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor, Types
>    Affects Versions: 3.0.0, 1.0.0, 4.0.0
>            Reporter: Chaoyu Tang
>            Assignee: Karen Coppage
>            Priority: Major
>             Fix For: 4.0.0
>
>         Attachments: HIVE-10362.01.patch, HIVE-10362.02.patch, 
> HIVE-10362.03.patch, HIVE-10362.04.patch, HIVE-10362.04.patch, 
> HIVE-10362.06.patch, HIVE-10362.07.patch
>
>
> There are quite a lot of issues associated with the non-noramlized or 
> type-mismatched values for partition column. Hive has many ways to introduce 
> such problematic data. HIVE-10307 mainly provides the support to type 
> check/convert/normalize the partition column value in static partition 
> specification. This JIRA tries to deal with the partition column type  in 
> dynamic partition insert. Currently any data can be inserted as a partition 
> column value as long as it is quoted as a string. For example,
> create table dynparttypechecknum (key int, value string) partitioned by (part 
> int);
> insert into dynparttypechecknum partition (part) select key, value, '00001' 
> from src limit 1;
> show partitions dynparttypechecknum;
> --
> part=00001
> The partition column value is non-normalized int 00001. It causes some 
> unnecessary problems such as integer partition column JDO filter pushdown 
> (see HIVE-6052) and others like HIVE-10210.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to