[
https://issues.apache.org/jira/browse/IMPALA-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-8087:
---------------------------------
Assignee: (was: bharath v)
> Evaluate to adapt the serde property values length as per the latest changes
> on HMS
> ------------------------------------------------------------------------------------
>
> Key: IMPALA-8087
> URL: https://issues.apache.org/jira/browse/IMPALA-8087
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 2.7.0
> Reporter: Adriano
> Priority: Major
> Labels: ramp-up
>
> Hi,
> with the HIVE-12274 (C5.13) seems that the SERDE_PARAMS.PARAM_VALUE max
> length is increased in all the supported RDBMS to a bigger value while on our
> side we kept to 4k (depending by the RDBMS the datatype used increased the
> length between 32k and 64k).
> I saw that those lines are not changed in the latest releases:
> https://github.com/cloudera/Impala/blob/cdh5-2.7.0_5.10.2/fe/src/main/java/org/apache/impala/util/MetaStoreUtil.java#L50-L51
>
> https://github.com/cloudera/Impala/blob/cdh5-2.7.0_5.10.2/fe/src/main/java/org/apache/impala/util/MetaStoreUtil.java#L145-L155
> Not sure if can be done without breaking anything, however could you evaluate
> if it is possible to safely increase it to a bigger value? If that case could
> you get this Jira in your backlog?
> It will allow as example the creation of avro table with avro.schema.literal
> > 4k as in Hive instead to exit with:
> {code:java}
> AnalysisException: Property value length must be <= 4000:
> {code}
> Thank you,
> Adriano
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
