hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13648) ORC Schema Evolution doesn't support same type conversion for VARCHAR, CHAR, or DECIMAL when maxLength or precision/scale is different
Date Tue, 14 Jun 2016 19:05:27 GMT

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

Prasanth Jayachandran commented on HIVE-13648:
----------------------------------------------

[~mmccline] I can see enforcing precision and scale in decimal conversion, but I don't see
enforcing change in maxLength for char/varchar conversion reader. Also fileType argument passed
StringGroupFromStringGroupTreeReader seems to be unused. 

> ORC Schema Evolution doesn't support same type conversion for VARCHAR, CHAR, or DECIMAL
when maxLength or precision/scale is different
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13648
>                 URL: https://issues.apache.org/jira/browse/HIVE-13648
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Matt McCline
>            Assignee: Matt McCline
>            Priority: Critical
>         Attachments: HIVE-13648.01.patch, HIVE-13648.02.patch
>
>
> E.g. when a data file is copied in has a VARCHAR maxLength that doesn't match the DDL's
maxLength.  This error is produced:
> {code}
> java.io.IOException: ORC does not support type conversion from file type varchar(145)
(36) to reader type varchar(114) (36)
> {code}



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

Mime
View raw message