[
https://issues.apache.org/jira/browse/HIVE-16710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017803#comment-16017803
]
Sergey Shelukhin commented on HIVE-16710:
-----------------------------------------
If it's set up for tests, name the patch HIVE-XXXXX.YY-branch-2.2.patch. If not
then this won't work.
+1 on the updated patch... I doubt the test run for this would actually be
useful, unless there's some obvious bug. Partial local run might suffice.
> Make MAX_MS_TYPENAME_LENGTH configurable
> ----------------------------------------
>
> Key: HIVE-16710
> URL: https://issues.apache.org/jira/browse/HIVE-16710
> Project: Hive
> Issue Type: Bug
> Reporter: Zhiyuan Yang
> Assignee: Zhiyuan Yang
> Fix For: 2.2.0
>
> Attachments: HIVE-16710.1.patch, HIVE-16710.2.patch
>
>
> HIVE-11985 introduced type name length check in 2.0.0. Before 2.3
> (HIVE-12274), users have no way to work around this check if they do get very
> long type name. We should make max type name length configurable before 2.3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
