You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/06/10 19:02:21 UTC

[jira] [Commented] (HIVE-13994) increase large varchar limits in db scripts to be db-specific

    [ https://issues.apache.org/jira/browse/HIVE-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325086#comment-15325086 ] 

Sergey Shelukhin commented on HIVE-13994:
-----------------------------------------

[~ashutoshc] [~sushanth] thoughts/objections?

> increase large varchar limits in db scripts to be db-specific
> -------------------------------------------------------------
>
>                 Key: HIVE-13994
>                 URL: https://issues.apache.org/jira/browse/HIVE-13994
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>
> Right now all our max varchar limits are 4k, presumably due to Oracle limitations. All other dbs support larger values and/or MAX; given that we moved away from schema auto-creation and towards db-specific scripts, we can increase these limits per database to maximum allowed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)