1 Answer
- Newest
- Most votes
- Most comments
1
That doesn't really depend on Glue, Glue brings the MySQL JDBC driver 8.0.23 (actually it is the same as Glue 3) and anything you pass in the url has to be supported by the driver:
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-configuration-properties.html#table-connector-j-connp-props-session
Notice the name of the parameters is not exactly the same as the properties when you set then inside the database
Thanks, your answer gave me a hint. I solved the problem by using the updated version of JDBC driver. Fyr, as I checked, Glue 4.0 and Glue 3.0 supports a same version of J driver so I downloaded the upper version from MySQL site.
Relevant content
- asked 2 years ago
- asked 4 years ago

Is it possible that the characters are already mixed up ? at that point? Have you tried to do a source_frame.show() and check in the output look it is correct before saving
@Gonzalo Herreros
The source dynamic frame was ok, I inserted the same frame into redshift before insert it into RDS and checked the string values are shown correctly in Redshift.
That will just use the standard MySQL connector, try using Glue 4.0 so you have a recent version of the driver. Have you ever tried to use those flags with MySQL JDBC before?
@Gonzalo Herreros Thanks for the suggestion. This is first time to use MySQL JDBC in Glue job. Could you advise which updates in Glue 4.0 makes recognize unicode & charset parameters in jdbc url that Glue 3.0 couldn't recognize? For your convienence, if there is any doc I can reference, just sharing it's link would be really helpful.