Misakami opened a new issue, #24311: URL: https://github.com/apache/shardingsphere/issues/24311
## Bug Report I used two sharding strategies for the same table This bug should have been fixed in 5.1, but I still encountered it in 5.3.0 see the issue [14273](https://github.com/apache/shardingsphere/issues/14273) ### Which version of ShardingSphere did you use? ShardingSphere-JDBC 5.3.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior no error ### Actual behavior NullPointerException ### Reason analyze (If you can) I used two sharding strategies for the same table but just load the first sharding strategies。 ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. see bug report this is part of my strategies tb_ration_trigger_trade_flow: actualDataNodes: ds$->{1..4}.ration_trigger_trade_flow_$->{1..8} keyGenerateStrategy: column: key_id keyGeneratorName: snowflake hint_ration_trigger_trade_flow: actualDataNodes: ds$->{1..4}.ration_trigger_trade_flow_$->{1..8} databaseStrategy: hint: shardingAlgorithmName: hint keyGenerateStrategy: column: key_id keyGeneratorName: asnowflake tableStrategy: hint: shardingAlgorithmName: hint ### 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]
