hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Vovchenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HIVE-13460) ANALYZE TABLE COMPUTE STATISTICS FAILED max key length is 1000 bytes
Date Fri, 08 Apr 2016 16:21:25 GMT
Aleksey Vovchenko created HIVE-13460:
----------------------------------------

             Summary: 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


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)

Mime
View raw message