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
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
When ModShardingAlgorithm is used and zeroPadding is true and the shards exceed 10, the first shard of table user should be user_00
Actual behavior
the first shard of table user be user_0
Reason analyze (If you can)
For the scenario where zeroPadding of ModShardingAlgorithm is true, org.apache.shardingsphere.infra.datanode.DataNodeUtils#getFormatDataNodes should be adjusted accordingly.
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).
The text was updated successfully, but these errors were encountered:
Aresxue
changed the title
zeroPadding in ModShardingAlgorithm
actualDataNodes is wrong when ModShardingAlgorithm's zeroPadding is true
Apr 29, 2024
Which version of ShardingSphere did you use?
5.4.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
When ModShardingAlgorithm is used and zeroPadding is true and the shards exceed 10, the first shard of table user should be user_00
Actual behavior
the first shard of table user be user_0
Reason analyze (If you can)
For the scenario where zeroPadding of ModShardingAlgorithm is true, org.apache.shardingsphere.infra.datanode.DataNodeUtils#getFormatDataNodes should be adjusted accordingly.
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).
The text was updated successfully, but these errors were encountered: