You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Matt McCline (JIRA)" <ji...@apache.org> on 2016/06/01 21:01:03 UTC
[jira] [Updated] (HIVE-13648) ORC Schema Evolution doesn't support
same type conversion for VARCHAR, CHAR, or DECIMAL when maxLength or
precision/scale is different
[ https://issues.apache.org/jira/browse/HIVE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt McCline updated HIVE-13648:
--------------------------------
Attachment: (was: HIVE-13648.01.patch)
> 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
>
>
> 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)