-
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
GA destinations: remove supportsDbt
and supportsNormalization
from spec.json
#21306
GA destinations: remove supportsDbt
and supportsNormalization
from spec.json
#21306
Conversation
Affected Connector ReportNOTE
|
Connector | Version | Changelog | Publish |
---|
- See "Actionable Items" below for how to resolve warnings and errors.
❌ Destinations (6)
Connector | Version | Changelog | Publish |
---|---|---|---|
destination-bigquery |
2.0.0 |
✅ | ❌ (diff seed version) |
destination-bigquery-denormalized |
1.2.10 |
✅ | ✅ |
destination-databricks |
0.3.1 |
✅ | ✅ |
destination-s3 |
1.0.0 |
✅ | ✅ |
destination-s3-glue |
0.1.1 |
✅ | ✅ |
destination-snowflake |
1.0.0 |
✅ | ❌ (diff seed version) |
- See "Actionable Items" below for how to resolve warnings and errors.
👀 Other Modules (1)
- base-normalization
Actionable Items
(click to expand)
Category | Status | Actionable Item |
---|---|---|
Version | ❌ mismatch |
The version of the connector is different from its normal variant. Please bump the version of the connector. |
⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
|
Changelog | ⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
❌ changelog missing |
There is no chnagelog for the current version of the connector. If you are the author of the current version, please add a changelog. | |
Publish | ⚠ not in seed |
The connector is not in the seed file (e.g. source_definitions.yaml ), so its publication status cannot be checked. This can be normal (e.g. some connectors are cloud-specific, and only listed in the cloud seed file). Please double-check to make sure that it is not a bug. |
❌ diff seed version |
The connector exists in the seed file, but the latest version is not listed there. This usually means that the latest version is not published. Please use the /publish command to publish the latest version. |
/test connector=connectors/destination-bigquery
Build PassedTest summary info:
|
/test connector=connectors/destination-snowflake
Build PassedTest summary info:
|
/test connector=connectors/destination-s3
Build PassedTest summary info:
|
NB: I don't think it's safe to merge until cloud is deployed with OSS >= |
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.
Nice!
- Major version bump (semver!)
- Docs explain why & what version of the platform is needed
- connector tests all pass
Cloud is now on >= 0.43.18. |
/publish connector=connectors/destination-bigquery
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/destination-snowflake
if you have connectors that successfully published but failed definition generation, follow step 4 here |
@airbytehq/use please checkout the changelog. |
@evantahler I realize that even if we remove these fields from The |
So the only benefit from the current PR would be confirming the platform 💯 relies on definitions to manage connector normalization. But I'm not sure it's worth the confusion of releasing connectors with |
@davydov-d let me know once you created the OAuth parameters on the Cloud DB and I'll approve the PR so that we can merge it tommorow. |
@alafanechere done |
I am confused as to how these changes affect the destinations. From the comment that you linked is sounds like if you merge this PR, normalization will be disabled for BigQuery and Snowflake destinations, which is not good. |
We now pull the information about the normalization / dbt support from the connector definition, so the connector spec is not used by the platform to determine if normlization is supported. So merging this PR should not break anything. My concern is that the spec output is going to be misleading: as the we remove these field from these connector spec their value will fallback to the default defined in the protocol model. So running |
This seems dangerous. Another question. If I am adding a new connector with normalization support - how do I do that without breaking the CI? I cannot add the connector to |
Closing to wait for the protocol update tracked here or the decoupling of java connectors from protocol models. |
What
Issue: https://github.com/airbytehq/airbyte-internal-issues/issues/2539
The source of truth for
supportsDbt
andsupportsNormalization
is now in the destination definition.We should remove it from the destination spec.
This PR is doing it for GA destinations.