[
https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445587#comment-16445587
]
Hive QA commented on HIVE-19250:
--------------------------------
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
2s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 1m 51s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-10364/dev-support/hive-personality.sh
|
| git revision | master / 9cfaf6b |
| modules | C: metastore U: metastore |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-10364/yetus.txt |
| Powered by | Apache Yetus http://yetus.apache.org |
This message was automatically generated.
> Schema column definitions inconsistencies in MySQL
> --------------------------------------------------
>
> Key: HIVE-19250
> URL: https://issues.apache.org/jira/browse/HIVE-19250
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 2.1.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Minor
> Attachments: HIVE-19250.patch
>
>
> There are some inconsistencies in column definitions in MySQL between a
> schema that was upgraded to 2.1 (from an older release) vs installing the
> 2.1.0 schema directly.
> > `CQ_TBLPROPERTIES` varchar(2048) DEFAULT NULL,
> 117d117
> < `CQ_TBLPROPERTIES` varchar(2048) DEFAULT NULL,
> 135a136
> > `CC_TBLPROPERTIES` varchar(2048) DEFAULT NULL,
> 143d143
> < `CC_TBLPROPERTIES` varchar(2048) DEFAULT NULL,
> 156c156
> < `CTC_TXNID` bigint(20) DEFAULT NULL,
> ---
> > `CTC_TXNID` bigint(20) NOT NULL,
> 158c158
> < `CTC_TABLE` varchar(256) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT
> NULL,
> ---
> > `CTC_TABLE` varchar(256) DEFAULT NULL,
> 476c476
> < `TBL_NAME` varchar(256) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT
> NULL,
> ---
> > `TBL_NAME` varchar(256) DEFAULT NULL,
> 664c664
> < KEY `PCS_STATS_IDX`
> (`DB_NAME`,`TABLE_NAME`,`COLUMN_NAME`,`PARTITION_NAME`),
> ---
> > KEY `PCS_STATS_IDX`
> > (`DB_NAME`,`TABLE_NAME`,`COLUMN_NAME`,`PARTITION_NAME`) USING BTREE,
> 768c768
> < `PARAM_VALUE` mediumtext,
> ---
> > `PARAM_VALUE` mediumtext CHARACTER SET latin1 COLLATE latin1_bin,
> 814c814
> < `PARAM_VALUE` mediumtext,
> ---
> > `PARAM_VALUE` mediumtext CHARACTER SET latin1 COLLATE latin1_bin,
> 934c934
> < `PARAM_VALUE` mediumtext,
> ---
> > `PARAM_VALUE` mediumtext CHARACTER SET latin1 COLLATE latin1_bin,
> 1066d1065
> < `TXN_HEARTBEAT_COUNT` int(11) DEFAULT NULL,
> 1067a1067
> > `TXN_HEARTBEAT_COUNT` int(11) DEFAULT NULL,
> 1080c1080
> < `TC_TXNID` bigint(20) DEFAULT NULL,
> ---
> > `TC_TXNID` bigint(20) NOT NULL,
> 1082c1082
> < `TC_TABLE` varchar(128) DEFAULT NULL,
> ---
> > `TC_TABLE` varchar(128) NOT NULL,
> 1084c1084
> < `TC_OPERATION_TYPE` char(1) DEFAULT NULL,
> ---
> > `TC_OPERATION_TYPE` char(1) NOT NULL,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
