-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Column index out of range. #34084
Comments
@HADESCH9 Can you modify this issue according to issue template? |
ok |
What is your SQL and configuration? |
Field mapping configuration file is as follows rules:
- !SINGLE
tables:
- "ds1.*"
- !ENCRYPT
tables:
vehicle_blacklist:
columns:
license_plate_number:
name: license_plate_number
cipher:
name: license_plate_number_cipher
encryptorName: aes_encryptor
likeQuery:
name: license_plate_number_cipher_col
encryptorName: like_queyr_encryptor Error occurred before and after updating the SQL, when Seata tried to retrieve the data before the update, an error was reported |
What is the database configuration and SQL details and table metadata? |
Bug Report
When integrating Seata with ShardingSphere-JDBC version 5.5.1, the following error occurred:
Which version of ShardingSphere did you use?
5.5.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
Actual behavior
error
Reason analyze (If you can)
I suspect that the issue arises from the "like" column configured for fuzzy search in the table.
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: