RaigorJiang commented on issue #25954:
URL: 
https://github.com/apache/shardingsphere/issues/25954#issuecomment-1579858038

   @wgijja 
   I tried to modify your yml configuration, and now it can be started 
successfully.
   ```yaml
   spring:
     shardingsphere:
   #    mode:
   #      type: Standalone
   #      repository:
   #        type: JDBC
       # 指定 YAML 配置文件
       dataSource:
         names: ds_3312
         ds_3312:
           type: com.zaxxer.hikari.HikariDataSource
           driverClassName: com.mysql.cj.jdbc.Driver
           jdbcUrl: jdbc:mysql://host:port/db_order
           username: root
           password: xxx
   
       rules:
         sharding:
           tables: # 数据分片规则配置
             t_order: # 逻辑表名称
               actualDataNodes: ds_3312.t_order$->{0..11}
               tableStrategy: # 分表策略,同分库策略
                 standard: # 用于单分片键的标准分片场景
                   shardingColumn: order_no # 分片列名称
                   shardingAlgorithmName: t_order_inline # 分片算法名称
   
               keyGenerateStrategy: # 分布式序列策略
                 column: id
                 keyGeneratorName: snowflake
   
           # 分片算法配置
           sharding-algorithms:
             t_order_inline: # 分片算法名称
               type: INLINE # 分片算法类型
               props: # 分片算法属性配置
                 algorithm-expression: t_order$->{order_no % 12} # ...
           # 分布式序列算法配置
           keyGenerators:
             snowflake: # 分布式序列算法名称
               type: SNOWFLAKE # 分布式序列算法类型
               # ...
   
       props:
         sql-show: true
   ```
   The previous problems were mainly about keyword `shardingsphere` and 
datasource, refer to 
[quick-start](https://shardingsphere.apache.org/document/5.2.0/en/quick-start/shardingsphere-jdbc-quick-start/).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to