chrissata opened a new issue #6226: URL: https://github.com/apache/shardingsphere/issues/6226
## Bug Report **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? 4.1.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior DML of broadcast table route to the right datasources. ### Actual behavior DML of broadcast table route to the all datasources. But ddl route strategy is right. ### Reason analyze (If you can) DML of broadcast table use all datasources as target. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1) config. schemaName: test_db dataSources: ds0: xxxx ds1: xxxx ds2: xxxx shardingRule: tables: testGlobal: actualDataNodes: ds${0..1}.testGlobal broadcastTables: - testGlobal 2) do DML sql use test_db update testGlobal set name="abc"; ### Example codes for reproduce this issue (such as a github link). update or insert sql ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
