ShardingSphere5.0自定义分表策略

 需要根据SPI来注入

META-INF/services/org.apache.shardingsphere.sharding.spi.ShardingAlgorithm

内容:com.example.user.sharding.UserIdSharding

Java代码

@Data
public class UserIdSharding implements StandardShardingAlgorithm<String> {
    private static final String SHARDING_COUNT_KEY = "sharding-count";

    /**
     * 对应props配置
     */
    private Properties props = new Properties();

    private int shardingCount;

    /**
     * 初始化调用
     */
    @Override
    public void init() {
        shardingCount = getShardingCount();
    }

    private int getShardingCount() {
        Preconditions.checkArgument(props.containsKey(SHARDING_COUNT_KEY), "Sharding count cannot be null.");
        return Integer.parseInt(props.get(SHARDING_COUNT_KEY).toString());
    }
    /**
     * Standard Sharding
     * @param availableTargetNames real table
     * @param preciseShardingValue Single Sharding key
     * @return
     */
    @Override
    public String doSharding(Collection<String> availableTargetNames, PreciseShardingValue<String> preciseShardingValue) {
        long l = Long.parseLong(preciseShardingValue.getValue()) % shardingCount;
        for (String availableTargetName : availableTargetNames) {
            if (availableTargetName.endsWith(String.valueOf(l))) {
                return availableTargetName;
            }
        }

        return null;
    }

    /**
     * Complex Sharding
     * @param availableTargetNames real table
     * @param rangeShardingValue Multiple Sharding Key
     * @return
     */
    @Override
    public Collection<String> doSharding(Collection<String> availableTargetNames, RangeShardingValue<String> rangeShardingValue) {
        return null;
    }

    /**
     * SPI根据配置Type获取
     * @return
     */
    @Override
    public String getType() {
        return "USER_ID";
    }

配置

spring:
  config:
    activate:
      on-profile: prod
  shardingsphere:
    datasource:
      names: master,slave
      master:
        type: com.alibaba.druid.pool.DruidDataSource
        driver-class-name: com.mysql.cj.jdbc.Driver
        url: jdbc:mysql://asus:3306/auth_db?characterEncoding=UTF-8&serverTimezone=Asia/Shanghai&autoReconnect=true&failOverReadOnly=false&zeroDateTimeBehavior=convertToNull&useSSL=false
        username: auth_user
        password: zxc521cxzPass!
      slave:
        type: com.alibaba.druid.pool.DruidDataSource  # 数据库配置,配置属性名 不同连接池,连接名不一样。根据数据库连接池DataSource来配置
        driver-class-name: com.mysql.cj.jdbc.Driver
        url: jdbc:mysql://dell:3306/auth_db?characterEncoding=UTF-8&serverTimezone=Asia/Shanghai&autoReconnect=true&failOverReadOnly=false&zeroDateTimeBehavior=convertToNull&useSSL=false
        username: auth_user
        password: zxc521cxzPass!
    props:
      sql-show: true
    rules:
      readwrite-splitting:
        load-balancers:
          roundRobin:
            type: ROUND_ROBIN #从库路由算法,ROUND_ROBIN:轮询,RANDOM:随机
        data-sources:
          read-write_0:
            #自动发现数据源名称(配置动态读写分离规则显示),库中不配置则读写分离不生效,不配置则为静态分离,可以动态扩容。
            #只支持MySQL的自动发现,可以拓展成根据配置进行动态扩容?
            #auto_aware_data_source_name
            load-balancer-name: roundRobin #轮询算法
            read-data-source-names: slave #读库
            write-data-source-name: master #写库
      sharding:
        tables:
          users:
            table-strategy:
              standard:
                sharding-algorithm-name: table-inline
                sharding-column: user_id
            actual-data-nodes: read-write_0.users_$->{0..1}  #read-write_0 为读写分离的逻辑表明
        sharding-algorithms:
          table-inline:
            type: USER_ID
            props:
              sharding-count: 2

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Sharding-JDBC 是一款基于 JDBC 的分布式数据库中间件,它提供了分库分表、读写分离、分布式事务等功能。而自定义分表策略就是 Sharding-JDBC 中非常重要的一部分。 下面我来介绍一下如何自定义分表策略以及实战实例: 1. 自定义分表策略 Sharding-JDBC 自带了一些默认的分表策略,例如按照取模分表、按照日期分表等。但如果默认分表策略不能满足我们的需求,我们可以自定义分表策略自定义分表策略需要实现 `PreciseShardingAlgorithm` 接口,该接口包含两个方法: - `doSharding(Collection<String> availableTargetNames, PreciseShardingValue shardingValue)`:根据分片键和可用的分片数据源名称集合进行分片计算,返回分片后的数据源名称。 - `getType()`:返回分片算法名称。 下面是一个自定义按照用户 ID 分表分表策略: ```java public class UserIdShardingAlgorithm implements PreciseShardingAlgorithm<Long> { @Override public String doSharding(Collection<String> availableTargetNames, PreciseShardingValue<Long> shardingValue) { for (String tableName : availableTargetNames) { if (tableName.endsWith(shardingValue.getValue() % 10)) { return tableName; } } throw new UnsupportedOperationException(); } @Override public String getType() { return "USER_ID"; } } ``` 2. 实战实例 下面是一个使用 Sharding-JDBC 的 Spring Boot 实战示例,该示例演示了如何使用自定义分表策略按照用户 ID 分表: 1. 引入依赖: ```xml <dependency> <groupId>org.apache.shardingsphere</groupId> <artifactId>sharding-jdbc-spring-boot-starter</artifactId> <version>${sharding-jdbc.version}</version> </dependency> ``` 2. 编写配置文件: ```yaml spring: shardingsphere: datasource: names: ds0, ds1 ds0: driver-class-name: com.mysql.cj.jdbc.Driver url: jdbc:mysql://localhost:3306/db0?useSSL=false&serverTimezone=GMT%2B8&useUnicode=true&characterEncoding=UTF-8&allowPublicKeyRetrieval=true username: root password: root ds1: driver-class-name: com.mysql.cj.jdbc.Driver url: jdbc:mysql://localhost:3306/db1?useSSL=false&serverTimezone=GMT%2B8&useUnicode=true&characterEncoding=UTF-8&allowPublicKeyRetrieval=true username: root password: root sharding: tables: user: actual-data-nodes: ds$->{0..1}.user_$->{0..9} table-strategy: inline: sharding-column: user_id algorithm-expression: user_$->{user_id % 10} key-generator: column: user_id type: SNOWFLAKE default-database-strategy: inline: sharding-column: user_id algorithm-expression: ds$->{user_id % 2} props: sql.show: true ``` 3. 编写自定义分表策略: ```java public class UserIdShardingAlgorithm implements PreciseShardingAlgorithm<Long> { @Override public String doSharding(Collection<String> availableTargetNames, PreciseShardingValue<Long> shardingValue) { for (String tableName : availableTargetNames) { if (tableName.endsWith(shardingValue.getValue() % 10)) { return tableName; } } throw new UnsupportedOperationException(); } @Override public String getType() { return "USER_ID"; } } ``` 4. 在 Spring Boot 中配置自定义分表策略: ```java @Configuration public class ShardingConfig { @Autowired private DataSource dataSource; @Bean public ShardingRule shardingRule() { TableRule userTableRule = TableRule.builder("user") .actualTables(Arrays.asList("user_0", "user_1", "user_2", "user_3", "user_4", "user_5", "user_6", "user_7", "user_8", "user_9")) .dataSourceRule(dataSourceRule()) .tableShardingStrategy(new TableShardingStrategy("user_id", new UserIdShardingAlgorithm())) .keyGenerator(new KeyGeneratorConfiguration("SNOWFLAKE", "user_id")) .build(); return ShardingRule.builder() .dataSourceRule(dataSourceRule()) .tableRules(Arrays.asList(userTableRule)) .databaseShardingStrategy(new DatabaseShardingStrategy("user_id", new InlineShardingStrategy("user_id", "ds$->{user_id % 2}"))) .build(); } @Bean public DataSourceRule dataSourceRule() { Map<String, DataSource> dataSourceMap = new HashMap<>(); dataSourceMap.put("ds0", createDataSource("ds0")); dataSourceMap.put("ds1", createDataSource("ds1")); return new DataSourceRule(dataSourceMap); } private DataSource createDataSource(final String dataSourceName) { DruidDataSource result = new DruidDataSource(); result.setDriverClassName("com.mysql.cj.jdbc.Driver"); result.setUrl(String.format("jdbc:mysql://localhost:3306/%s?useSSL=false&serverTimezone=GMT%%2B8&useUnicode=true&characterEncoding=UTF-8&allowPublicKeyRetrieval=true", dataSourceName)); result.setUsername("root"); result.setPassword("root"); return result; } @Bean public DataSource dataSource() throws SQLException { return new ShardingDataSource(shardingRule()); } } ``` 在上面的示例中,我们使用了自定义的按照用户 ID 分表分表策略。在 `ShardingConfig` 类中,我们使用 `DataSourceRule` 和 `ShardingRule` 配置数据源和分片规则,并且使用自定义分表策略和分库策略。在 `application.yaml` 文件中,我们配置了数据源和表的分片规则以及自定义分表策略。 以上就是关于如何自定义分表策略以及实战实例的介绍。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值