[ https://issues.apache.org/jira/browse/HIVE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760823#comment-13760823 ]
Jason Dere commented on HIVE-4844: ---------------------------------- The max varchar length setting was pretty arbitrary, sure we can have it set to a lower value. Any ideas on what value to initially set? 32,767 (small enough to fit within a short), or maybe something even smaller like 1024, just to make the point that we don't want enormous varchar columns that require checking the string length? > Add varchar data type > --------------------- > > Key: HIVE-4844 > URL: https://issues.apache.org/jira/browse/HIVE-4844 > Project: Hive > Issue Type: New Feature > Components: Types > Reporter: Jason Dere > Assignee: Jason Dere > Attachments: HIVE-4844.10.patch, HIVE-4844.11.patch, > HIVE-4844.12.patch, HIVE-4844.1.patch.hack, HIVE-4844.2.patch, > HIVE-4844.3.patch, HIVE-4844.4.patch, HIVE-4844.5.patch, HIVE-4844.6.patch, > HIVE-4844.7.patch, HIVE-4844.8.patch, HIVE-4844.9.patch, > HIVE-4844.D12699.1.patch, screenshot.png > > > Add new varchar data types which have support for more SQL-compliant > behavior, such as SQL string comparison semantics, max length, etc. > Char type will be added as another task. > NO PRECOMMIT TESTS - now dependent on HIVE-5203/5204/5206 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira