[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-19250: --- Fix Version/s: (was: 3.1.0) 4.0.0 > 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 > Fix For: 4.0.0 > > Attachments: HIVE-19250.patch, 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)
[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-19250: --- Fix Version/s: (was: 3.0.0) > 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 > Fix For: 3.1.0 > > Attachments: HIVE-19250.patch, 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)
[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naveen Gangam updated HIVE-19250: - Resolution: Fixed Fix Version/s: 3.1.0 3.0.0 Status: Resolved (was: Patch Available) > 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 > Fix For: 3.0.0, 3.1.0 > > Attachments: HIVE-19250.patch, 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)
[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naveen Gangam updated HIVE-19250: - Status: Open (was: Patch Available) pre-commits did not run. Retrying > 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, 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)
[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naveen Gangam updated HIVE-19250: - Attachment: HIVE-19250.patch > 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, 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)
[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naveen Gangam updated HIVE-19250: - Status: Patch Available (was: Open) > 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, 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)
[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naveen Gangam updated HIVE-19250: - Attachment: HIVE-19250.patch > 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)
[jira] [Updated] (HIVE-19250) Schema column definitions inconsistencies in MySQL
[ https://issues.apache.org/jira/browse/HIVE-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naveen Gangam updated HIVE-19250: - Status: Patch Available (was: Open) [~aihuaxu] [~vihangk1] Could you please review? Thanks > 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)
