liulipengju opened a new issue, #19516: URL: https://github.com/apache/shardingsphere/issues/19516
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 5.1.2 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior config encrypt field is normal ### Actual behavior nested exception is java.lang.IllegalArgumentException: Invalid encrypt column configurations in EncryptTableRuleConfigurations. ### Reason analyze (If you can) I think that config is correct, Because refer examples，it could be internal code judgment problem ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. spring: shardingsphere: datasource: ...... rules: encryptors: common-encryptor: type: AES props: aes-key-value: 12345678s encrypt: tables: t_school: columns: school_name: cipher-column: school_name encryptor-name: common-encryptor school_code: cipher-column: school_code encryptor-name: common-encryptor score: cipher-column: score encryptor-name: common-encrypt when delete score field, it is ok, when added, it will be exception， Is score a keyword? ### 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]
