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/15 08:57:09 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15331407#comment-15331407 ]
Matt McCline edited comment on HIVE-13648 at 6/15/16 8:56 AM:
--------------------------------------------------------------
[~prasanth_j]
Hi Prasanth,
Thanks for you review.
When converting from CHAR(N) to CHAR(M), the StringGroupFromStringGroupTreeReader class is used. It calls convertStringGroupVectorElement to do any necessary trimming/length adjustment.
The Q files have cases for converting to smaller and larger maxLength, etc.
Yes, I saw that when the row reader stuff was removed a bunch of not used members / parameters appeared. I had already removed them in the patch that Sergey is currently reviewing.
Matt
was (Author: mmccline):
[~prasanth_j]
Hi Prasanth,
Thanks for you review.
When converting from CHAR(N) to CHAR(M), the StringGroupFromStringGroupTreeReader class is used. It calls convertStringGroupVectorElement to do any necessary trimming/length adjustment.
Yes, I saw that when the row reader stuff was removed a bunch of not used members / parameters appeared. I had already removed them in the patch that Sergey is currently reviewing.
Matt
> 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)