02-25更新依赖方法
S2B2C 白洞版 · 02-25更新依赖方法
2025-02-25更新依赖方法
Section titled “2025-02-25更新依赖方法”示例值注意事项:本文中的 IP、域名、账号、密码等仅为示例,请按你的实际环境替换。
- 适用于二开技术团队在对应模块下的开发、调试或配置工作。
- 已拉取对应项目源码并具备基础运行环境。
- 已根据实际环境替换文中的示例配置值。
如果你的依赖已经是最新版本,即2025年2月25号之后的版本,就不用更新依赖了。如果你是旧版,你不想更新依赖也不影响系统使用。
1. seata2.0更新到2.2
Section titled “1. seata2.0更新到2.2”需要增加mysql的jar依赖,以及编辑seata已配置挂载好的配置文件application.yml里面的seata.store.db,变成这种格式(vgroup-table这个参数很重要):
db: datasource: druid db-type: mysql # 需要根据mysql的版本调整driverClassName # mysql8及以上版本对应的driver:com.mysql.cj.jdbc.Driver # mysql8以下版本的driver:com.mysql.jdbc.Driver driver-class-name: com.mysql.cj.jdbc.Driver url: jdbc:mysql://192.168.1.41:3306/mall4cloud_seata?useUnicode=true&characterEncoding=utf8&connectTimeout=1000&socketTimeout=3000&autoReconnect=true&useSSL=false&rewriteBatchedStatements=true user: root password: hn02le.34lkdLKD min-conn: 10 max-conn: 100 global-table: global_table branch-table: branch_table lock-table: lock_table distributed-lock-table: distributed_lock vgroup-table: vgroup_table query-limit: 1000 max-wait: 50002. nacos 2.3.2升级到2.5.0 表结构发生变化
Section titled “2. nacos 2.3.2升级到2.5.0 表结构发生变化”USE `mall4cloud_nacos`;
/* Alter table in target */ALTER TABLE `config_info` CHANGE `group_id` `group_id` VARCHAR(128) COLLATE utf8mb3_bin NULL COMMENT 'group_id' AFTER `data_id` , CHANGE `app_name` `app_name` VARCHAR(128) COLLATE utf8mb3_bin NULL COMMENT 'app_name' AFTER `src_ip` , CHANGE `c_desc` `c_desc` VARCHAR(256) COLLATE utf8mb3_bin NULL COMMENT 'configuration description' AFTER `tenant_id` , CHANGE `c_use` `c_use` VARCHAR(64) COLLATE utf8mb3_bin NULL COMMENT 'configuration usage' AFTER `c_desc` , CHANGE `effect` `effect` VARCHAR(64) COLLATE utf8mb3_bin NULL COMMENT '配置生效的描述' AFTER `c_use` , CHANGE `type` `type` VARCHAR(64) COLLATE utf8mb3_bin NULL COMMENT '配置的类型' AFTER `effect` , CHANGE `c_schema` `c_schema` TEXT COLLATE utf8mb3_bin NULL COMMENT '配置的模式' AFTER `type` , CHANGE `encrypted_data_key` `encrypted_data_key` VARCHAR(1024) COLLATE utf8mb3_bin NOT NULL DEFAULT '' COMMENT '密钥' AFTER `c_schema` ;
/* Alter table in target */ALTER TABLE `config_info_beta` CHANGE `encrypted_data_key` `encrypted_data_key` VARCHAR(1024) COLLATE utf8mb3_bin NOT NULL DEFAULT '' COMMENT '密钥' AFTER `tenant_id` ;
/* Create table in target */CREATE TABLE `config_info_gray` ( `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` VARCHAR(255) NOT NULL COMMENT 'data_id', `group_id` VARCHAR(128) NOT NULL COMMENT 'group_id', `content` LONGTEXT NOT NULL COMMENT 'content', `md5` VARCHAR(32) DEFAULT NULL COMMENT 'md5', `src_user` TEXT COMMENT 'src_user', `src_ip` VARCHAR(100) DEFAULT NULL COMMENT 'src_ip', `gmt_create` DATETIME(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) COMMENT 'gmt_create', `gmt_modified` DATETIME(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) COMMENT 'gmt_modified', `app_name` VARCHAR(128) DEFAULT NULL COMMENT 'app_name', `tenant_id` VARCHAR(128) DEFAULT '' COMMENT 'tenant_id', `gray_name` VARCHAR(128) NOT NULL COMMENT 'gray_name', `gray_rule` TEXT NOT NULL COMMENT 'gray_rule', `encrypted_data_key` VARCHAR(256) NOT NULL DEFAULT '' COMMENT 'encrypted_data_key', PRIMARY KEY (`id`), UNIQUE KEY `uk_configinfogray_datagrouptenantgray` (`data_id`,`group_id`,`tenant_id`,`gray_name`), KEY `idx_dataid_gmt_modified` (`data_id`,`gmt_modified`), KEY `idx_gmt_modified` (`gmt_modified`)) ENGINE=INNODB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 COMMENT='config_info_gray';
/* Alter table in target */ALTER TABLE `config_tags_relation` CHANGE `nid` `nid` BIGINT NOT NULL AUTO_INCREMENT COMMENT 'nid, 自增长标识' AFTER `tenant_id` ;
/* Alter table in target */ALTER TABLE `his_config_info` ADD COLUMN `publish_type` VARCHAR(50) DEFAULT 'formal' COMMENT 'publish type gray or formal', ADD COLUMN `gray_name` VARCHAR(50) DEFAULT NULL COMMENT 'gray name', ADD COLUMN `ext_info` LONGTEXT DEFAULT NULL COMMENT 'ext info';
/* Alter table in target */ALTER TABLE `permissions` CHANGE `role` `role` VARCHAR(50) COLLATE utf8mb4_general_ci NOT NULL COMMENT 'role' FIRST , CHANGE `resource` `resource` VARCHAR(128) COLLATE utf8mb4_general_ci NOT NULL COMMENT 'resource' AFTER `role` , CHANGE `action` `action` VARCHAR(8) COLLATE utf8mb4_general_ci NOT NULL COMMENT 'action' AFTER `resource` , COLLATE ='utf8mb4_general_ci' ;
/* Alter table in target */ALTER TABLE `roles` CHANGE `username` `username` VARCHAR(50) COLLATE utf8mb4_general_ci NOT NULL COMMENT 'username' FIRST , CHANGE `role` `role` VARCHAR(50) COLLATE utf8mb4_general_ci NOT NULL COMMENT 'role' AFTER `username` , COLLATE ='utf8mb4_general_ci' ;
/* Alter table in target */ALTER TABLE `users` CHANGE `username` `username` VARCHAR(50) COLLATE utf8mb4_general_ci NOT NULL COMMENT 'username' FIRST , CHANGE `password` `password` VARCHAR(500) COLLATE utf8mb4_general_ci NOT NULL COMMENT 'password' AFTER `username` , CHANGE `enabled` `enabled` TINYINT(1) NOT NULL COMMENT 'enabled' AFTER `password` , COLLATE ='utf8mb4_general_ci' ;/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;3. shardingsphere 更新到5.5
Section titled “3. shardingsphere 更新到5.5”-
需要删除
server.yaml中的sqlCommentParseEnabled -
同时增加
commons-collections4-4.5.0-M3.jar到shardingsphere挂载目录下的ext-lib文件夹
4. mongodb升级到7.0
Section titled “4. mongodb升级到7.0”需要将数据先全部导出来,更新之后再导入,并且移除storage.journal.enabled: true这个参数
- 根据文中步骤完成后,确认对应功能可访问或服务可正常启动。
- 可先查看故障排查索引:
../../../04-故障排查/README.md
- 当前目录索引:
README.md