2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 2 anni fa
0
I am too struggling with same issue. Has anyone found resolution on this?
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
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.