ssxlulu commented on issue #4861: two tables left join with different routing rules are not supported URL: https://github.com/apache/incubator-shardingsphere/issues/4861#issuecomment-604267702 > > When the shardingsphere route the sql, it does not find the table b's sharding key, so it will cause a full route. > > To avoid it, you may add the table b's sharding key after where condition.And now shardingsphere may not use the condition after 'on' clause. > > In the future，Whether shardingsphere can be considered ‘on’ after join? because by convention, For old system upgrades， only write main table's sharding value after 'where' 。 > or add config like bindtables ，to achieve this function It depends on requirement and the implementation of the route algorithm. In my opinion, shardingsphere may not considered the 'on' clause for routing.
---------------------------------------------------------------- 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 With regards, Apache Git Services
