mayfsac opened a new issue, #17076: URL: https://github.com/apache/shardingsphere/issues/17076
## 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? I am using 5.0.0 but the same as 5.1.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior   the three columns both are belone to one table but actially mapping more than one table ### Actual behavior  ### Reason analyze (If you can)  there are same columns of the uniqueTables , then The key-value of map will be overwritten multiple times ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. select * from a left join (select * from b where id = 1 and sid =1 and zid =1 ) B on a.sid =B.sid left join (select * from c where id = 1 and zid =1 ) table a contains id sid ,table b contains id sid zid ,table c contains id zid ### 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]
