Chris Cranford

Hi @jaegwonseo there is an outstanding question on the Jira issue, if you could answer that.

Hi @ggaborg can you please run the check style check using: ``` ./mvnw clean install -DskipITs -DskipTests ``` Also, thanks for the contribution, but there was also a discussion on...

Hi @debjeetsarkar so first off I don't have any issues upgrading the binlog client version in `main`, I'd prefer we avoid this in the `1.9` branch unless there is an...

@jpechane should we consider moving from the `.jre8` desigator to `.jre11` since Debezium requires JDK11 now? _UPDATE_ There appear to be some build failures related to this change, I'm looking...

Hi @jpechane it does. It looks like in 10.2, quite a lot of breaking changes: https://docs.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#changes-in-102 Specifically to this problem, `encrypt` is enabled by default whereas in 9.4 it was...

So @jpechane, I simply explicitly disabled the encryption for our test suite. According to this link: https://techcommunity.microsoft.com/t5/azure-database-support-blog/pkix-path-building-failed-unable-to-find-valid-certification/ba-p/2591304 We will need to download and import the TLS1 and TLS2 certificates using...

@vjuranek since Jiri is on PTO, do you have any preference or opinion on this PR?

It would be an incompatibility that would require connector reconfiguration by adding `database.encrypt=false` if they don't use encryption but with the volume of SQL Server users with issues with TLSv1...

So here's a thought to maintain backward compatibility. In prior versions, if you wanted to support encryption, `database.encrypt` and all the driver bits had to be provided by the user....

In order to use encryption with the docker container, it would appear we need to follow these steps: https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-docker-container-security?view=sql-server-ver16 This basically involves: - Creating `.key` and `.pem` files - Supplying...