max key length is 767 bytes

最新推荐文章于 2024-08-02 04:09:35 发布
最新推荐文章于 2024-08-02 04:09:35 发布
阅读量2.2k 收藏
点赞数
分类专栏： Bigdatda-Hive 问题解决 文章标签： max key length is 76
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/baolibin528/article/details/45423173
版权 
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes

错误描述：
hive> load data local inpath "/root/partition_table.dat" into table partition_table partition(class="job1");
Loading data to table mydb.partition_table partition (class=job1)
Failed with exception MetaException(message:javax.jdo.JDODataStoreException: Error(s) were found while auto-creating/validating the datastore for classes. The errors are printed in the log, and are attached to this exception.
        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.addPartition(ObjectStore.java:1431)
        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:98)
        at com.sun.proxy.$Proxy5.addPartition(Unknown Source)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.append_partition_common(HiveMetaStore.java:1888)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.append_partition_with_environment_context(HiveMetaStore.java:1943)
        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:102)
        at com.sun.proxy.$Proxy6.append_partition_with_environment_context(Unknown Source)
        at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.appendPartition(HiveMetaStoreClient.java:531)
        at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.appendPartition(HiveMetaStoreClient.java:525)
        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.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:90)
        at com.sun.proxy.$Proxy7.appendPartition(Unknown Source)
        at org.apache.hadoop.hive.ql.metadata.Hive.getPartition(Hive.java:1730)
        at org.apache.hadoop.hive.ql.metadata.Hive.loadPartition(Hive.java:1349)
        at org.apache.hadoop.hive.ql.metadata.Hive.loadPartition(Hive.java:1269)
        at org.apache.hadoop.hive.ql.exec.MoveTask.execute(MoveTask.java:428)
        at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
        at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:85)
        at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1604)
        at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1364)
        at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1177)
        at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1004)
        at org.apache.hadoop.hive.ql.Driver.run(Driver.java:994)
        at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:247)
        at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:199)
        at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:410)
        at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:783)
        at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:677)
        at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:616)
        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.util.RunJar.run(RunJar.java:221)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
NestedThrowablesStackTrace:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes
        at sun.reflect.GeneratedConstructorAccessor49.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:3597)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2619)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2569)
        at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:813)
        at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:656)
        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.TableImpl.createIndices(TableImpl.java:648)
        at org.datanucleus.store.rdbms.table.TableImpl.createConstraints(TableImpl.java:422)
        at org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.performTablesValidation(RDBMSStoreManager.java:3459)
        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.addPartition(ObjectStore.java:1431)
        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:98)
        at com.sun.proxy.$Proxy5.addPartition(Unknown Source)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.append_partition_common(HiveMetaStore.java:1888)
        at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.append_partition_with_environment_context(HiveMetaStore.java:1943)
        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:102)
        at com.sun.proxy.$Proxy6.append_partition_with_environment_context(Unknown Source)
        at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.appendPartition(HiveMetaStoreClient.java:531)
        at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.appendPartition(HiveMetaStoreClient.java:525)
        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.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:90)
        at com.sun.proxy.$Proxy7.appendPartition(Unknown Source)
        at org.apache.hadoop.hive.ql.metadata.Hive.getPartition(Hive.java:1730)
        at org.apache.hadoop.hive.ql.metadata.Hive.loadPartition(Hive.java:1349)
        at org.apache.hadoop.hive.ql.metadata.Hive.loadPartition(Hive.java:1269)
        at org.apache.hadoop.hive.ql.exec.MoveTask.execute(MoveTask.java:428)
        at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
        at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:85)
        at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1604)
        at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1364)
        at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1177)
        at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1004)
        at org.apache.hadoop.hive.ql.Driver.run(Driver.java:994)
        at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:247)
        at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:199)
        at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:410)
        at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:783)
        at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:677)
        at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:616)
        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.util.RunJar.run(RunJar.java:221)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
)
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.MoveTask


==============================================================该方法没解决我问题 start==================================================
网上找的这个方法没有解决我的问题

解决方法：
修改mysql.ini 文件：

default-character-set=utf8

character-set-server=utf8

修改完后，重启mysql的服务，service mysql restart
使用 mysql> SHOW VARIABLES LIKE 'character%';查看




修改之前的：
mysql> SHOW VARIABLES LIKE 'character%';
+--------------------------+---------------------------------------------------------+
| Variable_name            | Value                                                   |
+--------------------------+---------------------------------------------------------+
| character_set_client     | gbk                                                     |
| character_set_connection | gbk                                                     |
| character_set_database   | gbk                                                     |
| character_set_filesystem | binary                                                  |
| character_set_results    | gbk                                                     |
| character_set_server     | gbk                                                     |
| character_set_system     | utf8                                                    |
| character_sets_dir       | D:\Program Files\MySQL\MySQL Server 5.5\share\charsets\ |
+--------------------------+---------------------------------------------------------+
8 rows in set (0.00 sec)

mysql>



//修改之后的
mysql> SHOW VARIABLES LIKE 'character%';
+--------------------------+---------------------------------------------------------+
| Variable_name            | Value                                                   |
+--------------------------+---------------------------------------------------------+
| character_set_client     | utf8                                                    |
| character_set_connection | utf8                                                    |
| character_set_database   | utf8                                                    |
| character_set_filesystem | binary                                                  |
| character_set_results    | utf8                                                    |
| character_set_server     | utf8                                                    |
| character_set_system     | utf8                                                    |
| character_sets_dir       | D:\Program Files\MySQL\MySQL Server 5.5\share\charsets\ |
+--------------------------+---------------------------------------------------------+
8 rows in set (0.00 sec)

mysql>

==============================================================该方法没解决我问题 stop==================================================



============================================================下面这个方法解决了我的问题 start======================================
//解决方法：
在mysql机器的上运行:

alter database hive character set latin1;


//在Windows上的mysql上面执行：
mysql> alter database hive character set latin1;
Query OK, 1 row affected (0.02 sec)

mysql>



//hive加载分区表数据的语句成功执行了：
hive> load data local inpath "/root/aa.dat" into table t5 partition(class="job1");
Loading data to table default.t5 partition (class=job1)
Partition default.t5{class=job1} stats: [numFiles=2, numRows=0, totalSize=36, rawDataSize=0]
OK
Time taken: 3.931 seconds
hive>



============================================================下面这个方法解决了我的问题 stop======================================

礼彬fly
关注
专栏目录
建索引时或执行sql文件报 Specified key was too long； max key length is 767 bytes 错误的处理
qq_36173200的博客
09-02 584
原因 由于 MySQLInnodb 引擎表索引字段长度的限制为 767 字节，因此对于多字节字符集的大字段（或者多字段组合索引），创建索引会出现上面的错误。 以 utf8mb4 字符集 字符串类型字段为例：utf8mb4 是 4 字节字符集，则默认支持的索引字段最大长度是： 767 字节 / 4 字节每字符 = 191 字符，因此在 varchar(255) 或 char(255) 类型字段上创建索引会失败。 解决步骤 1.查看innodb_large_prefix，innodb_file_for.
mysql 索引过长1071-max key length is 767 byte
海边的豆豆的博客
04-10 3455
问题 由于系统需要，吧mysql数据库字符集由utf-8转换成utf-8mb4. mysql数据库中存在数据，那么不能直接用命令修改字符集，如果直接修改，只会对新创建的表或记录有效，原有数据还是之前的字符集。具体如下 导出存储sql（结构和数据） 替换存储sql中建表内容 CHARSET=utf8 =》CHARSET=utf8mb4 COLLATE utf8_unicode_ci =》COLL...
MySQL 异常：max key length is 767 bytes
分享既学习
06-26 1684
最近迁移几张表，又遇到 767 异常，迁移前只检查了 sql_mode 忽略对比了这个参数，导致几张表创建失败，其实解决方法也很简单，开启参数重新导入即可。该 ERROR 常发生在字符串类型的大字段上，本篇文章详细解读该问题。
mysql max key length 修改索引长度限制
最新发布
weixin_30905039的博客
08-02 94
我整理的一些关于【MySQL,SQL】的项目学习资料（附讲解～～）和大家一起分享、学习一下：https://edu.51cto.com/surl=QDW3g3如何修改MySQL的最大索引长度 在使用MySQL数据库时，可能会遇到因为索引长度限制而导致的错误。这篇文章将帮你了解如何修改MySQL最大索引长度限制。我们将通过...
hive的Specified key was too long; max key length is 767 bytes问题解决
数据库天地
12-06 401
上次安装hive时遇到很多问题，最后遗留下一个没有解决的问题，最后通过询问得以解决在这记录下：方便遇到同样问题的人： 问题阐述 在安装完hive后，执行： [root@localhost hive]# hive Hive history file=/tmp/root/hive_job_log_root_201112071228_90457717.txt hive> 创建表： hive...
Specified key was too long; max key length is 767 bytes
weixin_34008784的博客
03-18 109
在Hive里创建表时出现了错误： 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/vali...
MySQL错误“Specified key was too long; max key length is 1000 bytes”的解决办法
09-11
max key length is 1000 bytes”。这个错误意味着你试图创建的索引键（key）超过了MySQL允许的最大长度。MySQL对每个表的每个索引都有一个最大长度限制，通常是1000字节。这个限制包括了所有被索引字段的长度。 在...
解决MySQL Specified key was too long； max key length is 767 bytes
ミ安之偌素
05-01 1286
最近在给QA测试环境数据表的一个的**varchar(255)**类型字段添加索引时遇到了错误Specified key was too long; max key length is 767 bytes，奇怪的是同样的创建索引命令是可以在开发环境执行成功的。 我们知道InnoDB引擎索引字段长度不能超过767，所以在排查问题时，我的第一反应是数据表的字符集配置有问题。 utf8mb4 字符集是 1个字符=4个字节， varchar255字节长度 = 255 * 4=1020字节 utf8 字符集是 1个
[Err] 1071 - Specified key was too long; max key length is 767 bytes
热门推荐
：）
04-07 1万+
另外一台服务器到期了 所以新购了一台服务器 今天安装好了环境 准备将数据迁移过来 执行导入SQL：source /data/sql/77dh_20200407_2034.txt 发现报错如下 ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes 搜索得知需要将如下变量设置为如下值： innodb...
Zabbix5.0-插入数据库文件时报错：Specified key was too long； max key length is 767 bytes
和忘了饭香一起学习
06-05 612
Zabbix5.0-插入数据库文件时报错：Specified key was too long; max key length is 767 bytes 背景：之前成功安装过zabbix3.0、zabbix4.0转战5.0时出错： 执行：zcat /usr/share/doc/zabbix-server-mysql*/create.sql.gz | mysql -uzabbix -p zabbix 报错：Specified key was too long; max key length is 767 by
django单元测试 Specified key was too long; max key length is 767 bytes
Monster_ixx的博客
04-27 541
就这个错误弄了我一下午？ 本来打算写一些单元测试的case，结果就遇到了这个错误。原因可能是因为django model中某个表字段过长，而单元测试可能需要以这些字段作为索引所导致的。 最开始报错 django.db. utils.OperationalError: ( 1071，'Specified key was too long; max key length is 767 bytes') ...
Specified key was too long； max key length is 767 bytes解决方案
小蜜蜂1010的博客
02-22 1万+
公司使用的mysql数据库版本是5.6.51 在往里边导入sql语句时候，总是提示Specified key was too long; max key length is 767 bytes 导致上面报错的原因是由于InnoDB表的索引长度限制，在MySQL5.6版本后引入了参数innodb_large_prefix可以解决这个问题。该参数控制是否允许单列的索引长度超过767字节，有ON和OFF两个取值： ON ：Innodb表的行记录格式是Dynamic或Compressed的前提下，单列索引
Mysql max key length is 767 bytes
weixin_33670713的博客
06-29 2679
1.mysql 执行quartz 表发生异常： Specified key was too long; max key length is 767 bytes 解决方法： 1.重新建立数据库，不要使用utf8mdb4,要使用utf-8 查看默认字符集(默认情况下，mysql的字符集是latin1(ISO_8859_1) 通常，查看系统的字符集和排序方式的设定可以通过下面的两条命令： mysql&g...
1071 - Specified key was too long； max key length is 767 bytes
csdn565973850的博客
03-30 3911
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 3833
问题报错信息“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是三字节的...
[MYSQL]数据同步提示:Specified key was too long；max key length is 767 bytes
移动的130
08-11 359
查看MYSQL版本：5.6.45 数据库字符集：utf8 排序规则：utf8_general_ci Specified key was too long;max key length is 767 bytes 谷歌翻译：指定的密钥太长；最大密钥长度为767字节 查看资料发现是索引字段长度超限，5.6版本最大长度为767字节； 一般来说varchar或text类型设置为索引很容易出现这个问题，utf8一个字符占用3字节，若设置255长度，则为765字节；若设置长度为256，则为768字节；很容易超
key was too long; max key length is 767 bytes')；
lanbooli的专栏
06-12 856
mysql在执行脚本时，报出了以下错误： index column size too large. the maximum column size is 767 bytes 原因： INNODB 引擎，UTF-8，主键字符串 默认最大 767，需要修改 解决方案： 1. 对数据库进行设置 set global innodb_file_format = BARRACUDA se...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值