-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🎉 Destination MSSQL: added custom JDBC parameters support. #13054
Conversation
@pcsoni89 I don't see changes on the UI specification regarding additional JDBC params, does this parameter exist? |
/test connector=connectors/destination-mssql
|
@pcsoni89 cannot approve until the next things won't be done:
Thanks. |
Added bump files and changelog. |
/test connector=connectors/destination-mssql
|
/test connector=connectors/destination-mssql
Build PassedTest summary info:
|
@alexandertsukanov do you approve now that @pcsoni89 has made the changes? |
@alafanechere Looks like the version in Dockerfile is still not bumped here |
Bumped looks like this could be published and merged. But I want to re-run the tests again. |
/test connector=connectors/destination-mssql
Build PassedTest summary info:
|
/test connector=connectors/destination-mssql-strict-encrypt
Build PassedTest summary info:
|
9695114
to
6be3425
Compare
/publish connector=connectors/destination-mssql
|
/publish connector=connectors/destination-mssql-strict-encrypt
|
What
Add support for MSSQL Destinations to take in a JDBC URL Params input to specify any additional JDBC parameters for the connection.
This is a follow up to #10421
This is part of #9501
How
AbstractJdbcDestination can already handle jdbc parameters via the jdbc_url_params field, but the MSSQLDestination spec does not specify that field. We should update the spec to support additional jdbc parameters for MSSQL destination
Recommended reading order
1.AbstractJdbcDestination.java
2.MSSQLDestination.java
🚨 User Impact 🚨
For existing destination oracle connections, a new parameter i.e. JDBC URL Params will be displayed.It is an optional field and accepts key=value data. There won't be any impact on existing operations.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changesTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.