Hi, I was trying to sync data from my postgres to mysql db what was not able to complete it. Got this error

ERROR () LineGobbler(voidCall):85 - Exception in thread "main" java.lang.RuntimeException: com.mysql.cj.jdbc.exceptions.MysqlDataTruncation: Data truncation: Invalid JSON text: "Invalid escape character in string." at position 49 in value for column '_airbyte_tmp_rvq_user._airbyte_data'.

Including the full log here:

it sounds like it’s due to a value from the table

user

of your source that contains some escape characters not recognized by MySQL, it would help to find what row is the culprit though…

But, the user table has only one row, and it doesn’t seem like to have any escape character

Could you please maybe try to make a sync with only the table user from your postgres to mysql to see if it isolates and reproduces the error?

Ya sure

ya tried for the

user

table, and got the same error. Excluded the

user

table, and it ran fine for other tables.

can you share the log of the failing sync with only

user

?

are you sure there is no “invisible” escape characters in your

user

table? is it really a value of

postgres

?

Found in the information_schema that the table really has many columns, but not sure why it is showing a single row with single column. Will check there. Thanks for the help.

Found the issue, the specific column in the

user

has some encrypted text there, with special characters like $, / , etc., I think that’s the reason. But how can we sync for columns with that,..

@Boopathy Raja you can get the generated SQL from normalization module and try to run manually and discovery what should be done to resolve the issue with the escape. After that is possible to add to the Airbyte normalization module. I can help you, WDYT?

Thank U for your help here sir. But the problem is there even with no normalization. (i.e.) loading the _airbyte_raw_table_ itself.

It is giving error on the json building for raw_table, I guess

You're right! This is are production tables or testing one?

These are production tables. But since that column under error reason, is not required, I skipped the column. But, I wanted to get the proper approach to solve this problem.

Let me know if there anything that you need help besides that @Boopathy Raja