Closed y-ken closed 1 year ago
Do I better to follow this way? https://github.com/embulk/embulk-input-jdbc/pull/237#issuecomment-1202003618
Yeah, if you're in a hurry for the issue, please follow: https://github.com/embulk/embulk-input-jdbc/pull/237#issuecomment-1202003618
We're thinking about the plan to upgrade. But I guess things would happen after the Embulk core v0.11 is out.
Gotcha
just in case, which file is expected to specify driver_path?
I'm not sure. We use mysql-connector from Maven Central, not mysql.com.
OK, got it! I will try to use this https://mvnrepository.com/artifact/mysql/mysql-connector-java/5.1.49 has link for this file https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.49/mysql-connector-java-5.1.49.jar
Hi @hiroyuki-sato
I know we would better to switch Connector/J 8.X, prior to that, how about to use latest current JDBC minor version?
Since I'm facing
javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify
error with following combination, I'm wondering whether I need to use later version of JDBC Driver.According to this article, it recommend to use more later version of JDBC. https://tech.omablo.com/archives/1042 https://takeda-san.hatenablog.com/entry/2019/01/24/004526
From release note, there are mention about SSL related improvent. https://docs.oracle.com/cd/E17952_01/connector-j-5.1-relnotes-en/news-5-1-49.html
Therefore I feel better to use latest of 5.1.x series of JDBC Driver as default. that driver are released on Apr 20, 2020. it was 3 years ago.