SEZ9 commented on issue #8346:
URL: https://github.com/apache/seatunnel/issues/8346#issuecomment-5215603273
Confirmed: the connector delegates connection creation to
io.debezium.connector.sqlserver.SqlServerConnection, which constructs its own
URL, so extra parameters in `base-url` (like `encrypt` and
`trustServerCertificate`) are not propagated. A fix should parse the
user-provided URL parameters and pass them through as `database.encrypt` /
driver properties in the Debezium config.
As a possible workaround on 2.3.8, try passing the options via `debezium`
properties in the source config, e.g. `debezium { "database.encrypt" = "true",
"database.trustServerCertificate" = "true" }`, and report back whether that
resolves the connection issue.
Please share the full error stack trace (the Error Exception section is
empty) and the SQL Server version, so maintainers can verify the failure mode
and add a regression test with the fix. PRs are welcome if you'd like to
contribute the improvement.
<!-- streview-comment:66 -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
