[
https://issues.apache.org/jira/browse/HIVE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302308#comment-14302308
]
Sushanth Sowmyan commented on HIVE-9456:
----------------------------------------
+1 to content, that looks reasonable to me.
There is one other thing to take care of though, before committing this.
[~vikram.dixit]/[~brocknoland]/[~alangates] : given that it's not 0.15 anymore
but 1.2, what's the plan for db upgrade scripts? Should we have a 0.14->1.0
without this, a 1.0->1.1 without this, and 1.1->1.2 with this?
> Make Hive support unicode with MSSQL as Metastore backend
> ---------------------------------------------------------
>
> Key: HIVE-9456
> URL: https://issues.apache.org/jira/browse/HIVE-9456
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.14.0
> Reporter: Xiaobing Zhou
> Assignee: Xiaobing Zhou
> Attachments: HIVE-9456.1.patch
>
>
> There are significant issues when Hive uses MSSQL as metastore backend to
> support unicode, since MSSQL handles varchar and nvarchar datatypes
> differently. Hive 0.14 metastore mssql script DDL was using varchar as
> datatype, which can't handle multi-bytes/unicode characters, e.g., Chinese
> chars. This JIRA is going to track implementation of unicode support in that
> case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
