[
https://issues.apache.org/jira/browse/HIVE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720905#comment-16720905
]
yucai commented on HIVE-4844:
-----------------------------
[~jdere], [~ashutoshc], we found varchar and string will behave differently for
non-standard utf8 characters.
For example, the original data is
6130373530633166313366306B35B0A546386A8DAEAB62B4526F273464613936 in hex.
*B0A5 and* *8DAEAB* are non-standard utf8 characters, they are encoded to
EFBFBD if the data type is varchar, but string will not change it. So:
VARCHAR in hex shows:
6130373530633166313366306B35EFBFBDEFBFBD46386AEFBFBDEFBFBDEFBFBD62EFBFBD526F273464613936
STRING in hex shows:
6130373530633166313366306B35B0A546386A8DAEAB62B4526F273464613936
Is it expected?
> 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
> Priority: Major
> Fix For: 0.12.0
>
> Attachments: HIVE-4844.1.patch.hack, HIVE-4844.10.patch,
> HIVE-4844.11.patch, HIVE-4844.12.patch, HIVE-4844.13.patch,
> HIVE-4844.14.patch, HIVE-4844.15.patch, HIVE-4844.16.patch,
> HIVE-4844.17.patch, HIVE-4844.18.patch, HIVE-4844.19.patch,
> 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, HIVE-4844.D12891.1.patch, HIVE-4844.v12.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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
