-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Remove additionalProperties: false
from JDBC destination connectors
#14618
Remove additionalProperties: false
from JDBC destination connectors
#14618
Conversation
/test connector=connectors/destination-oracle
Build PassedTest summary info:
|
/test connector=connectors/destination-oracle-strict-encrypt
Build PassedTest summary info:
|
/test connector=connectors/destination-snowflake
Build PassedTest summary info:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the plan to have a couple other PRs for related connectors? I'm aware of destination-databricks and destination-mssql both being affected, not sure if there are others
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please don't forget the remaining destinations
/test connector=connectors/destination-databricks
Build PassedTest summary info:
|
/test connector=connectors/destination-mssql
Build PassedTest summary info:
|
/test connector=connectors/destination-mssql-strict-encrypt
Build PassedTest summary info:
|
/test connector=connectors/destination-oracle-strict-encrypt
Build PassedTest summary info:
|
/publish connector=connectors/destination-snowflake
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-mssql
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-databricks
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-oracle-strict-encrypt auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-mssql-strict-encrypt auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-oracle-strict-encrypt auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
…tions' of https://github.com/airbytehq/airbyte into vmaltsev/14550-remove-additionalproperties-jdbc-destinations
…tions' of https://github.com/airbytehq/airbyte into vmaltsev/14550-remove-additionalproperties-jdbc-destinations
…tions' of https://github.com/airbytehq/airbyte into vmaltsev/14550-remove-additionalproperties-jdbc-destinations
@grishick seems like publish of oracle-destination was cancelled after 4 hours. Please advice how to avoid this behaviour |
@benmoriceau is also publishing new versions of all destination connectors, so you can merge this PR w/o publishing |
* Bump oracle version number to match #14618 * Removed additionalProperties: false from oracle * remove additionalProperties:true from destination oracle specs * Mark 0.1.17 as unpublished, because it was never pushed to Docker Hub Co-authored-by: grishick <[email protected]>
…rbytehq-master * 'master' of https://github.com/airbytehq/airbyte: (1141 commits) pass USE_STREAM_CAPABLE_STATE env var to containers/deployments (airbytehq#14737) Bump mqtt connector (airbytehq#14648) Add error code to ManualOperationResult (airbytehq#14657) Bump elasticsearch version (airbytehq#14640) Ryan/sync oracle version number (airbytehq#14736) Fixed linter issue with add_fields.py comments (airbytehq#14742) 🎉Redshift, Databricks, Snowflake, S3 Destinations: Make S3 output filename configurable (airbytehq#14494) 🐛Source-mssql: aligned regular and cdc syncs and its datatype tests (airbytehq#14379) 🎉 Source Amazon Seller Partner: Add new streams (airbytehq#13604) bump source-file-secure (airbytehq#14704) 🎉 New source: Timely airbytehq#13292 (airbytehq#14335) 🪟🔧 Refactor feature service (airbytehq#14559) [low code cdk] add a transformation for adding fields into an outgoing record (airbytehq#14638) Bump destination-postgres to 0.3.21 (airbytehq#14479) Remove `additionalProperties: false` from JDBC destination connectors (airbytehq#14618) 🎉 Source Notion: add OAuth authorization for source-notion connector (airbytehq#14706) Use the configuration diff calculation in the update endpoint (airbytehq#14626) 🪟 🐛 Fix input validation on blur and cleanup signup error handling (airbytehq#14724) lower sleep after wait for successful job (airbytehq#14725) Add configuration diff (airbytehq#14603) ...
@VitaliiMaltsev I forgot about source-tidb in this PR. It's definitely lower-priority so feel free to just combine it with the followup issue. (unless @grishick you think it's worth handling separately) |
|
What
As discovered in airbytehq/oncall#289, a spec declaring "additionalProperties": false introduces the risk of accidental breaking changes. Specifically, when removing a property from the spec, existing connector configs will no longer be valid.
To make these upgrades/rollbacks smoother, we need to remove additionalProperties from connectors affected by these changes.
How
Remove additionalProperties: false
Recommended reading order
x.java
y.python
🚨 User Impact 🚨
none
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New 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 exampledocs/integrations/README.md
airbyte-integrations/builds.md
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.