当前位置：首页 > news >正文

shardingsphere-proxy分片+字段加密配置例子

news 2026/5/12 10:18:25

说明：

1.若是对表进行了分片同时也加密，配置在database-sharding.yaml文件中修改

2.单纯只是加密不分片，只需要在database-encrypt.yaml配置文件中修改

database-sharding.yaml

######################################################################################################
#
# If you want to connect to MySQL, you should manually copy MySQL driver to lib directory.
#
######################################################################################################databaseName: hxl_sharding_dbdataSources:ds_0:url: jdbc:mysql://192.168.1.113:3306/db_test?useSSL=false
    username: rootpassword: yeemiao3040connectionTimeoutMilliseconds: 30000idleTimeoutMilliseconds: 60000maxLifetimeMilliseconds: 1800000maxPoolSize: 50minPoolSize: 1
#  ds_1:
#    url: jdbc:mysql://127.0.0.1:3306/demo_ds_1?useSSL=false
#    username: root
#    password:
#    connectionTimeoutMilliseconds: 30000
#    idleTimeoutMilliseconds: 60000
#    maxLifetimeMilliseconds: 1800000
#    maxPoolSize: 50
#    minPoolSize: 1
#
rules:
- !SHARDINGtables:t_order:actualDataNodes: ds_0.t_order_${0..9}tableStrategy:standard:shardingColumn: order_idshardingAlgorithmName: t_order_inlinekeyGenerateStrategy:column: order_idkeyGeneratorName: snowflake
##      auditStrategy:
##        auditorNames:
##          - sharding_key_required_auditor
##        allowHintDisable: truetb_test:actualDataNodes: ds_0.tb_test_${0..9}tableStrategy:standard:shardingColumn: idshardingAlgorithmName: tb_test_inlinekeyGenerateStrategy:column: idkeyGeneratorName: snowflake
##      auditStrategy:
##        auditorNames:
##          - sharding_key_required_auditor
##        allowHintDisable: truetb_link:actualDataNodes: ds_0.tb_link_${0..9}tableStrategy:standard:shardingColumn: user_idshardingAlgorithmName: tb_link_inlinekeyGenerateStrategy:column: idkeyGeneratorName: snowflake
##      auditStrategy:
##        auditorNames:
##          - sharding_key_required_auditor
##        allowHintDisable: true#    t_order_item:
#      actualDataNodes: ds_${0..1}.t_order_item_${0..1}
#      tableStrategy:
#        standard:
#          shardingColumn: order_id
#          shardingAlgorithmName: t_order_item_inline
#      keyGenerateStrategy:
#        column: order_item_id
#        keyGeneratorName: snowflake
#  bindingTables:
#    - t_order,t_order_item
#  defaultDatabaseStrategy:
#    standard:
#      shardingColumn: user_id
#      shardingAlgorithmName: database_inline
#  defaultTableStrategy:
#    none:
##  defaultAuditStrategy:
##    auditorNames:
##      - sharding_key_required_auditor
##    allowHintDisable: true
#shardingAlgorithms:
#    database_inline:
#      type: INLINE
#      props:
#        algorithm-expression: ds_${user_id % 2}t_order_inline:type: INLINEprops:algorithm-expression: t_order_${order_id % 10}tb_test_inline:type: INLINEprops:algorithm-expression: tb_test_${id % 10}tb_link_inline:type: INLINEprops:algorithm-expression: tb_link_${user_id % 10}#    t_order_item_inline:
#      type: INLINE
#      props:
#        algorithm-expression: t_order_item_${order_id % 2}
#keyGenerators:snowflake:type: SNOWFLAKE##  auditors:
##    sharding_key_required_auditor:
##      type: DML_SHARDING_CONDITIONS
#
#- !BROADCAST
#  tables:
#    - t_address- !ENCRYPTencryptors:aes_encryptor:type: AESprops:aes-key-value: 123456abcdigest-algorithm-name: SHA-1tables:tb_link:columns:name1:cipher:name: name1encryptorName: aes_encryptor

表结构：

CREATE TABLE tb_link (`id` bigint NOT NULL COMMENT '主键id',`user_id` bigint DEFAULT NULL COMMENT '用户id',`name1` varchar(64) DEFAULT NULL COMMENT '姓名1',`name2` varchar(64) DEFAULT NULL COMMENT '姓名2',`name3` varchar(64) DEFAULT NULL COMMENT '姓名3',`name4` varchar(64) DEFAULT NULL COMMENT '姓名4',`name5` varchar(64) DEFAULT NULL COMMENT '姓名5',`name6` varchar(64) DEFAULT NULL COMMENT '姓名6',`name7` varchar(64) DEFAULT NULL COMMENT '姓名7',`name8` varchar(64) DEFAULT NULL COMMENT '姓名8',`name9` varchar(64) DEFAULT NULL COMMENT '姓名9',`name10` varchar(64) DEFAULT NULL COMMENT '姓名10',PRIMARY KEY (`id`),KEY `user_id` (`user_id`)
) ENGINE=InnoDB;