tiya-9975 commented on issue #37993: URL: https://github.com/apache/shardingsphere/issues/37993#issuecomment-3875465291
Thanks for the detailed reproduction steps and example @penghuazhou 👍 From the error message (Sharding value '[B@…' must implements Comparable), this looks like the sharding value is being treated as a byte[] when interpolateParams=false (prepared statement mode), which would explain why the COMPLEX_INLINE algorithm fails in 5.5.2 but worked in 5.1.1. A few clarifying questions that may help triage this as a regression: Does this reproduce with ShardingSphere-JDBC 5.5.2, or only with Proxy? Does it fail for both app_id and group_id, or only the VARCHAR sharding column? If you log parameter types on the proxy side, is group_id being received as byte[] instead of String? If this behavior worked in 5.1.1 with the same config, it likely indicates a regression in prepared-statement parameter handling for complex sharding algorithms. Happy to help test or narrow this down further. -- 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]
