strongyc opened a new issue, #20845: URL: https://github.com/apache/shardingsphere/issues/20845
## Bug Report Using version 5.1.2, after configuring read-write separation and data fragmentation, the fragmented table cannot be read from the slave library, and other tables can read from the slave library normally. Why **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 5.1.2 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC spring: shardingsphere: mode: type: Memory datasource: names: db1,db2 db1: driver-class-name: com.mysql.cj.jdbc.Driver jdbc-url: jdbc:mysql://192.168.37.130:3306/student?useUnicode=true&characterEncoding=utf-8&useSSL=false&serverTimezone=Asia/Shanghai username: root password: type: com.zaxxer.hikari.HikariDataSource db2: driver-class-name: com.mysql.cj.jdbc.Driver jdbc-url: jdbc:mysql://192.168.37.132:3306/student?useUnicode=true&characterEncoding=utf-8&useSSL=false&serverTimezone=Asia/Shanghai username: root password: type: com.zaxxer.hikari.HikariDataSource rules: sharding: tables: document: actual-data-nodes: db1.document_$->{2013..2022} table-strategy: standard: sharding-algorithm-name: document-inline # 分片算法名称 sharding-column: document_year key-generate-strategy: column: id key-generator-name: timestamp #主键生成算法#主键生成算法 sharding-algorithms: document-inline: type: INLINE props: algorithm-expression: document_$->{document_year} key-generators: timestamp: type: SNOWFLAKE readwrite-splitting: data-sources: read_write_db: type: Static props: write-data-source-name: db1 read-data-source-names: db2 load-balancer-name: round_robin load-balancers: round_robin: type: ROUND_ROBIN props: sql-show: true ### Expected behavior ### Actual behavior select use db2 ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. ### Example codes for reproduce this issue (such as a github link). -- 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]
