2 Answers
- Newest
- Most votes
- Most comments
0
After searching for a while, this is the only place I've seen this issue mentioned. I have the same issue except the MySQL timezone is "CDT". Adding "?serverTimezone=CST6CDT" to the connection string, allows the connection test to pass. However it appears a Crawler using the connection drops that connections string argument.
answered 2 years ago
0
I am too struggling with same issue. Has anyone found resolution on this?
answered a year ago
Relevant content
- asked 2 years ago
- asked 5 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
My workaround in it, is I just ends up directly connecting to my JDBC connection inside the Job, and just connected the JDBC connection to the Job.
Note: I just checked today, Test Connection in Connection does not work anymore but still able to connect inside the Job.