caol64 commented on issue #21083: URL: https://github.com/apache/shardingsphere/issues/21083#issuecomment-1257490798
> * For ShardingSphere 5.2.0 using SnakeYAML 1.30, there is a YAML deserialization bug first discovered in ShardingSphere that broke a unit test of ShardingSphere a few months ago, and was fixed not long ago at [Update snakeyaml to 1.32 to fix yaml deserialization problem #21048](https://github.com/apache/shardingsphere/pull/21048). > * This seems to be a duplicate of [shardingsphere5.2 cannot use druid with Password encryption #21032 (comment)](https://github.com/apache/shardingsphere/issues/21032#issuecomment-1250017446) for the unique handling of Alibaba Druid, because unit tests for Alibaba Druid never existed for ShardingSphere, which led to no discovery Possible issues with `org.apache.shardingsphere.infra.util.yaml.constructor.ShardingSphereYamlConstructor`. > * But anyway, it's impossible for anyone to know what's going on without anyone willing to provide an example.🤔 @linghengqian I provide an example: https://github.com/caol64/sharding-test. In version 5.2, It will throw an exception: Can't construct a java object for tag:yaml.org,2002:com.alibaba.druid.filter.stat.StatFilter; exception=Class is not accepted: com.alibaba.druid.filter.stat.StatFilter. Please check. -- 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]
