hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bharath v (JIRA)" <>
Subject [jira] [Commented] (HIVE-9815) Metastore column"SERDE_PARAMS"."PARAM_VALUE" limited to 4000 bytes
Date Mon, 21 Dec 2015 07:18:46 GMT


bharath v commented on HIVE-9815:

[~ngangam] This is a problem for table/db params too (both param_key and param_value) and
not just for serdes. I hope they are included in this jira's scope. Thanks.

> Metastore column"SERDE_PARAMS"."PARAM_VALUE"  limited to 4000 bytes
> -------------------------------------------------------------------
>                 Key: HIVE-9815
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.14.0
>            Reporter: Naveen Gangam
>            Assignee: Naveen Gangam
>            Priority: Critical
>         Attachments: Hv2.txt
> Currently, in the hive metastore schema, the length of the column SERDE_PARAMS.PARAM_VALUE
is set to 4000 bytes. This is not enough for users that have a key with a value larger than
4000 bytes. Say something like hbase.columns.mapping.
> I am not a database historian but appears that this limitation may have been put in place
because Oracle's varchar2 was restricted to 4k bytes for a long time until recently. 
> According to the following documentation, even today Oracle DB's varchar2 only supports
a max size of 4000 unless a configuration parameter MAX_STRING_SIZE is set to EXTENDED.
> {code}
> {code}
> Postgres supports a max of 1GB for character datatype according to
> MySQL can support upto 65535 bytes for the entire row. So long as the PARAM_KEY value
+ PARAM_VALUE is less than 65535, we should be good.
> SQL Server's varchar max length is 8000 and can go beyond using "varchar(max)".
> Derby's varchar can be upto 32672 bytes.

This message was sent by Atlassian JIRA

View raw message