You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Xiaobing Zhou (JIRA)" <ji...@apache.org> on 2015/01/24 02:20:34 UTC
[jira] [Resolved] (HIVE-9208) MetaStore DB schema inconsistent for
MS SQL Server in use of varchar/nvarchar
[ https://issues.apache.org/jira/browse/HIVE-9208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaobing Zhou resolved HIVE-9208.
---------------------------------
Resolution: Won't Fix
HIVE-9456 is going to change all varchar to nvarchar in 0.15 and provide upgrade script form 0.14 to 0.15, so there's no consistency issue like the case.
Marked it as won't fix.
> MetaStore DB schema inconsistent for MS SQL Server in use of varchar/nvarchar
> -----------------------------------------------------------------------------
>
> Key: HIVE-9208
> URL: https://issues.apache.org/jira/browse/HIVE-9208
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.14.0
> Reporter: Eugene Koifman
> Assignee: Xiaobing Zhou
> Attachments: HIVE-9208.1.patch, HIVE-9208.2.patch
>
>
> hive-schema-0.15.0.mssql.sql has PARTITIONS.PART_NAME as NVARCHAR but COMPLETED_TXN_COMPONENTS.CTC_PARTITON, COMPACTION_QUEUE.CQ_PARTITION, HIVE_LOCKS.HL_PARTITION, TXN_COMPONENTS.TC_PARTITION all use VARCHAR. This cannot be right since they all store the same value.
> the same is true of hive-schema-0.14.0.mssql.sql and the two corresponding hvie-txn-schema-... files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)