Hive 创建表报"Specified key was too long; max key length is 767 bytes" 错误

最新推荐文章于 2024-03-30 13:23:20 发布
最新推荐文章于 2024-03-30 13:23:20 发布
阅读量4.5k 收藏 2
点赞数
分类专栏： Hive学习 文章标签： Hive hadoop MySQL
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/NIITYZU/article/details/46606581
版权

Hive元数据库使用MySQL数据库，在使用Hive创建表的时候，报了以下错误：

hive>  create table base ( id  int, name string, address string) row format delimited fields terminated by ',';
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:javax.jdo.JDODataStoreException: An exception was thrown while adding/validating class(es) : Specified key was too long; max key length is 767 bytes
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes
        at sun.reflect.GeneratedConstructorAccessor27.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
        at com.mysql.jdbc.Util.getInstance(Util.java:386)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2002)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2163)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2618)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2568)
        at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:842)
        at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:681)
        at com.jolbox.bonecp.StatementHandle.execute(StatementHandle.java:254)
        at org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:760)
        at org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:711)
        at org.datanucleus.store.rdbms.table.AbstractTable.create(AbstractTable.java:425)
        at org.datanucleus.store.rdbms.table.AbstractTable.exists(AbstractTable.java:488)
        at org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.performTablesValidation(RDBMSStoreManager.java:3380)
        at org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.addClassTablesAndValidate(RDBMSStoreManager.java:3190)
        at org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.run(RDBMSStoreManager.java:2841)
        at org.datanucleus.store.rdbms.AbstractSchemaTransaction.execute(AbstractSchemaTransaction.java:122)
        at org.datanucleus.store.rdbms.RDBMSStoreManager.addClasses(RDBMSStoreManager.java:1605)
        at org.datanucleus.store.AbstractStoreManager.addClass(AbstractStoreManager.java:954)
        at org.datanucleus.store.rdbms.RDBMSStoreManager.getDatastoreClass(RDBMSStoreManager.java:679)
        at org.datanucleus.store.rdbms.RDBMSStoreManager.getPropertiesForGenerator(RDBMSStoreManager.java:2045)
        at org.datanucleus.store.AbstractStoreManager.getStrategyValue(AbstractStoreManager.java:1365)
        at org.datanucleus.ExecutionContextImpl.newObjectId(ExecutionContextImpl.java:3827)
        at org.datanucleus.state.JDOStateManager.setIdentity(JDOStateManager.java:2571)
        at org.datanucleus.state.JDOStateManager.initialiseForPersistentNew(JDOStateManager.java:513)
        at org.datanucleus.state.ObjectProviderFactoryImpl.newForPersistentNew(ObjectProviderFactoryImpl.java:232)
        at org.datanucleus.ExecutionContextImpl.newObjectProviderForPersistentNew(ExecutionContextImpl.java:1414)
        at org.datanucleus.ExecutionContextImpl.persistObjectInternal(ExecutionContextImpl.java:2218)
        at org.datanucleus.ExecutionContextImpl.persistObjectWork(ExecutionContextImpl.java:2065)
        at org.datanucleus.ExecutionContextImpl.persistObject(ExecutionContextImpl.java:1913)
        at org.datanucleus.ExecutionContextThreadedImpl.persistObject(ExecutionContextThreadedImpl.java:217)
        at org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:727)
        at org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:752)
        at org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:719)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:108)
        at com.sun.proxy.$Proxy0.createTable(Unknown Source)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1261)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:1294)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
        at com.sun.proxy.$Proxy12.create_table_with_environment_context(Unknown Source)
        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$create_table_with_environment_context.getResult(ThriftHiveMetastore.java:8016)
        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$create_table_with_environment_context.getResult(ThriftHiveMetastore.java:8000)
        at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
        at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
        at org.apache.hadoop.hive.metastore.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:48)
        at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

        at org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:451)
        at org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:732)
        at org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:752)
        at org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:719)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:108)
        at com.sun.proxy.$Proxy0.createTable(Unknown Source)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1261)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:1294)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
        at com.sun.proxy.$Proxy12.create_table_with_environment_context(Unknown Source)
        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$create_table_with_environment_context.getResult(ThriftHiveMetastore.java:8016)
        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$create_table_with_environment_context.getResult(ThriftHiveMetastore.java:8000)
        at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
        at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
        at org.apache.hadoop.hive.metastore.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:48)
        at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
NestedThrowablesStackTrace:


             参考其他资料得知，是MySQL数据库字符集与Hive hive-site.xml中定义的不一致导致的。hive-site.xml中定义如下： 

<property>
  <name>javax.jdo.option.ConnectionURL</name>
  <value>jdbc:mysql://192.168.2.39:3306/hive?characterEncoding=UTF-8</value>
</property>


解决办法：

  进入MySQL中，修改对应数据的默认编码： alter database hive character set latin1;即可



NIITYZU
关注
  • 0
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Hive创建表时报错，Specified key was too long; max key length is 767 bytes
杨鑫newlife的专栏
05-10 2984
Hive创建表时报错，Specified key was too long; max key length is 767 bytes
MySQL创建索引报错 Specified key was too long；max key length is 1000 bytes.
最新发布
十三月的博客
05-14 1340
MySQL对创建索引的大小有限制，一般索引键最大长度总和不能超过1000个字节。
hive的Specified key was too long; max key length is 767 bytes问题解决
虎猫
01-22 121
当在hive中show table 时如果报以下错时    FAILED: Error in metadata: javax.jdo.JDODataStoreException: Error(s) were found while auto-creating/validating the datastore for classes. The errors are printed in the ...
hive创建表是报错： Specified key was too long; max key length is 767 bytes
duncan
07-13 378
今天在hive客户端创建表时报错，具体操作如下   hive&gt; create table test2(id string); FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:javax.jdo.JDODataStoreE...
Hive建表报错 Specified key was too long; max key length is 767 bytes
要努力啊
08-29 475
hive 建表报错， 建表语句：create table test1(id string); 报错信息如下： FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:javax.jdo.JDODataStoreException: An ...
hive中创建表报错 Specified key was too long； max key length is 767 bytes
独立团团长李云龙 的博客
08-30 462
在创建表的时候碰上这个问题，记录下： 1.报错Specified key was too long; max key length is 767 bytes 2.Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:javax.jdo.JDODataSt...
1071 - Specified key was too long； max key length is 767 bytes
csdn565973850的博客
03-30 2307
1071 - Specified key was too long; max key length is 767 bytes 问题处理
【MySql】Specified key was too long； max key length is 767 bytes
Hyatt的博客
06-09 3407
问题报错信息“ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes”，其实意思就是“索引字段长度太长，超过了767bytes”。解决方法mysql的varchar索引字段只支持不超过767个字节或者768/2=384个双字节 或者767/3=255个三字节的字段 而GBK是双字节的，UTF8是三字节的...
Specified key was too long； max key length is 767 bytes
justsomebody126的专栏
01-18 162
utf8mb4 4 个字节，故 varchar 字段最长不能超过 191。 https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes 767 bytes is the stated prefix limitation for InnoDB tables in MySQL version 5.6 (and prior versions). It’s 1,0..
Hive报错之 Specified key was too long; max key length is 767 bytes
qq_34341930的博客
04-18 176
当我遇到这个错误的时候，hive客户端只给了我们一句话 如果你拿着这句话去百度，可能你还是找不到最针对的解决办法，有可能你就算解决了，也不知道为什么 所以我们要学会去看日志文件，看报错日志 Hive的日志文件在/tmp/root下面 看了之后再对症下药，这样效率高很多！！！ 针对我的这个报错，其实是hive数据库编码问题 具体的解释和说明请看这个大佬的博客 https://...
MySQL5.5 Specified key was too long; max key length is 767 bytes
XinShun的博客
06-30 776
参考：https://blog.csdn.net/chenjianhuideyueding/article/details/88426021 将SQL脚本文件中的SET utf8mb4 改为SET utf8
Specified key was too long; max key length is 767 bytes问题解决
热门推荐
书山路遥
02-28 9万+
Specified key was too long; max key length is 767 bytes 在做一次mysql数据表迁移的时候碰到了这个问题。通过查阅资料和文档，这个问题的大致原因如下： 在mysql5.6中索引列的最大长度为767个字节。 简单讲，就是如果你将某列加入到索引中，而索引的内容大于767个字节，那么将会出现这个错误。 而对于一般建表来说，我们使用的多是in...
mysql/mariadb 导入数据库报错：Specified key was too long； max key length is 767 bytes
weixin_43738907的博客
02-21 437
mysql/mariadb max key length is 767 bytes
Conmi的正确答案——mariadb问题：“Specified key was too long； max key length is 767 bytes”与“Index column si...”
Conmi的博客
05-13 898
平台：树莓派3B 系统：树莓派buster（debianbuster） 问题： Specified key was too long; max key length is 767 bytes Index column size too large. The maximum column size is 767 bytes. 解决方案： 进入配置文件 sudo nano /etc/mysql/mariadb.conf.d/50-server.cnf 插入以下内容到文件中 innodb_fil.
错误提示yntax error or access violation: 1071 Specified key was too long； max key length is 767 bytes
雾里看花的博客
01-11 319
yntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes
#1071 - Specified key was too long; max key length is 767 bytes
angelina_zf的博客
08-16 6281
#1071 - Specified key was too long; max key length is 767 bytes
ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
ccpit2b2c的专栏
11-15 213
今天在MySQL 5.6版本的数据库中修改InnoDB表字段长度时遇到了"ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes"错误,第一次遇到这个错误，遂花了点学习、研究过、总结这个问题。 我们先来创建一个测试表，构造这样的错误。 mysql> use MyDB; ...
Specified key was too long；Index column size too large. The maximum column size is 767 bytes.
车马去闲闲——落日满秋山
10-22 331
重新创建Mariadb数据库后，在导入时报了这两个错误： ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes ERROR 1709 (HY000): Index column size too large. The maximum column size is 767 bytes. 解决方案： 1、修改my.ini的[mysqld]下参数： innodb_file_format=barracuda
hive 删除报错Specified key was too long; max key length is 3072 bytes
04-10
当在Hive中删除数据时，如果遇到报错"Specified key was too long; max key length is 3072 bytes"，这通常是由于使用了超过3072字节的键值导致的。这个错误是因为Hive默认使用的是InnoDB存储引擎，而InnoDB对于索引...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值