You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Xuefu Zhang (JIRA)" <ji...@apache.org> on 2015/10/30 02:50:27 UTC
[jira] [Comment Edited] (HIVE-12299) Hive Column Data Type
definition in schema limited to 4000 characters - too small
[ https://issues.apache.org/jira/browse/HIVE-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981709#comment-14981709 ]
Xuefu Zhang edited comment on HIVE-12299 at 10/30/15 1:49 AM:
--------------------------------------------------------------
I think we are seeing how increasingly prominent the issue is. Link the related issue together: HIVE-12274, HIVE-11985.
was (Author: xuefuz):
I think we are seeing how increasingly prominent the issue is. Link the related issue together: HVIE-12274, HIVE-11985.
> Hive Column Data Type definition in schema limited to 4000 characters - too small
> ---------------------------------------------------------------------------------
>
> Key: HIVE-12299
> URL: https://issues.apache.org/jira/browse/HIVE-12299
> Project: Hive
> Issue Type: Improvement
> Components: Hive
> Reporter: Lakshmi Ramakrishnan
>
> The data type definitions in the table schema are limited to 4K characters - as per the code here: https://github.com/apache/hive/tree/master/metastore/scripts/upgrade/derby
> I checked quickly and all meta stores have similar schema definition for the column type.
> Is there any reason why this limit is low? We had a table that had defined a struct, which had over 200 columns and the column names were rather verbose (for readability). This caused a non-obvious failure like
> FAILED: IllegalArgumentException Error: : expected at the end of 'string:array<struct<xyz:string, .....'. Is it possible to make this configurable or at least increase it to something much higher?
> Additionally, there is no validation error that communicates this limitation to the user, it required non-trivial debugging and looking into the table definitions when it failed trying to parse what was essentially a truncated type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)