[
https://issues.apache.org/jira/browse/HIVE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760721#comment-13760721
]
Xuefu Zhang commented on HIVE-4844:
-----------------------------------
[~jdere] Looking at your latest patch, I'm wondering if you have given thought
on the max on varchar length. Right now you put Integer.MAX_VALUE as the max,
but majority of DBs has a smaller limit than that. (Mysql chose 65,535, for
instance.) Having a smaller max might leave room for optimization. I understand
that there is no standard regarding this, but I'm curious if we made a
conscious decision on that.
> 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
