[
https://issues.apache.org/jira/browse/HIVE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294244#comment-14294244
]
Xiaobing Zhou commented on HIVE-9456:
-------------------------------------
[~ekoifman] Here's test case.
{noformat}
1. New empty metastore's created with 0.14 schema.
2. upgrade-0.14.0-to-0.15.0.mssql.sql is run manually to get 0.14 metastore
upgraded to 0.15.
3. Double check it to make sure every orginal varchar column changed to
nvarchar.
{noformat}
As you suggested, it'd be better to do test in context HIVE/HIVE CLI/, e.g.,
1. New empty metastore's created with 0.14 schema.
2. create some hive tables/load real data
3. shutdown metastore server
4. run schemetool to do upgrade
5. start metastore server
6. query those tables inited in step 2 to make sure things are correct.
I will do that. Thanks!
> 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)
