You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
preview select*from t_order WHERE order_id IN (768017);
preview select*from t_order WHERE order_id IN (400037);
preview select*from t_order WHERE order_id IN (768017,400037);
The text was updated successfully, but these errors were encountered:
This configuration looks very special. It uses the same sharding field order_id to shard both the database and the table, and the names of the shard tables are different in each database.
To support this special usage, we can divide it into two steps: 1. Temporary solution, remove the ShardingRouteAlgorithmException check in StandardShardingStrategy to support this scenario; 2. Long-term solution, restore the ShardingRouteAlgorithmException check and support this usage in autoTables.
Bug Report
Which version of ShardingSphere did you use?
5.5.1-SNAPSHOT f205426
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
Sharding routing is correct
Actual behavior
Exception occurs
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
The text was updated successfully, but these errors were encountered: