[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2022-10-21 Thread Stamatis Zampetakis (Jira) 


 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stamatis Zampetakis updated HIVE-13460:
---
Fix Version/s: (was: 1.2.0)

I cleared the fixVersion field since this ticket is not resolved. Please review 
this ticket and if the fix is already committed to a specific version please 
set the version accordingly and mark the ticket as RESOLVED.

According to the JIRA guidelines 
(https://cwiki.apache.org/confluence/display/Hive/HowToContribute) the 
fixVersion should be set only when the issue is resolved/closed.

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
>Priority: Major
> Attachments: HIVE-13460-branch-1.0.patch, 
> HIVE-13460-branch.2-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-06-09 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: HIVE-13460-branch.2-1.0.patch

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.patch, 
> HIVE-13460-branch.2-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-08 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Status: Patch Available  (was: Open)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Attachments: HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-08 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: HIVE-13460-branch-1.0.patch

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Attachments: HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-11 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Fix Version/s: 1.2.0

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.2.patch, 
> HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-11 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: HIVE-13460-branch-1.0.2.patch

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Attachments: HIVE-13460-branch-1.0.2.patch, 
> HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-12 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: HIVE-13460-branch-1.0.3.patch

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.2.patch, 
> HIVE-13460-branch-1.0.3.patch, HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Status: In Progress  (was: Patch Available)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.2.patch, 
> HIVE-13460-branch-1.0.3.patch, HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Status: Patch Available  (was: In Progress)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.2.patch, 
> HIVE-13460-branch-1.0.3.patch, HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: (was: HIVE-13460-branch-1.0.patch)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.3.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: HIVE-13460-branch-1.0.patch

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: (was: HIVE-13460-branch-1.0.3.patch)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Status: Open  (was: Patch Available)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Status: Patch Available  (was: In Progress)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes

2016-04-14 Thread Aleksey Vovchenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HIVE-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Vovchenko updated HIVE-13460:
-
Attachment: (was: HIVE-13460-branch-1.0.2.patch)

> ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
> 
>
> Key: HIVE-13460
> URL: https://issues.apache.org/jira/browse/HIVE-13460
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Affects Versions: 1.0.1
>Reporter: Aleksey Vovchenko
>Assignee: Aleksey Vovchenko
> Fix For: 1.2.0
>
> Attachments: HIVE-13460-branch-1.0.3.patch, 
> HIVE-13460-branch-1.0.patch
>
>
> When Hive configured to Store Statistics in MySQL we have next error:
> {noformat} 
> 2016-04-08 15:53:28,047 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 767 bytes
> {noformat} 
> If set MySql properties as:
> {noformat} 
> set global innodb_large_prefix = ON;
> set global innodb_file_format = BARRACUDA;
> {noformat} 
> Now we have next Error:
> {noformat} 
> 2016-04-08 15:56:05,552 ERROR [main]: jdbc.JDBCStatsPublisher 
> (JDBCStatsPublisher.java:init(316)) - Error during JDBC initialization.
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was 
> too long; max key length is 3072 bytes
> {noformat} 
>  As a result of my investigation I figured out that MySQL does not allow to 
> create primary key with size more than 3072 bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)