[
https://issues.apache.org/jira/browse/HIVE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt McCline updated HIVE-13648:
--------------------------------
Description:
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}
was:
New ORC data type conversion has some edges cases like CHAR/VAR different max
lengths and DECIMAL different scale/precision that need attention.
Also, wondering if some of the orc_* Q test failures (HIVE-13178 patch 092)
were due to DECIMAL data type precision not being copied correctly?
> 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
>
> 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)
