-
Notifications
You must be signed in to change notification settings - Fork 2
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
Charset Conversion Error #62
Comments
@djamadeus, I am going to release version 2.1.0 in a couple of minutes. This version uses the latest virtual-schema-common-jdbc library that contains a Virtual Schema property called IMPORT_DATA_TYPES. You can use that to switch between the two variants of result set type calculation, either calculated by Exasol or inferred from JDBC metadata. While the later mechanism is less efficient, it handles situation in a more forgiving way where the JDBC driver reports character set information inconsistently. |
Version 2.1.0 is released. |
awesome. will run some teste between holidays and give you feedback. |
The same issue described and solved here:
exasol/mysql-virtual-schema#26
also exists with this adapter.
ETL-3009: [Column=13 Row=2] [Charset conversion from 'UTF-8' to 'ASCII' failed [Invalid or incomplete multibyte or wide character]]
Switching back to 9.0.4-release solved the problem for me.
The text was updated successfully, but these errors were encountered: