-
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 supportsNormalization + supportsDbt from sources spec #21317
remove supportsNormalization + supportsDbt from sources spec #21317
Conversation
Affected Connector ReportNOTE
|
Connector | Version | Changelog | Publish |
---|---|---|---|
source-bigquery |
0.2.3 |
✅ | ✅ |
source-kafka |
0.2.3 |
✅ | ✅ |
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Destinations (0)
Connector | Version | Changelog | Publish |
---|
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Other Modules (0)
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/source-bigquery
Build PassedTest summary info:
|
/test connector=connectors/source-clickhouse
Build FailedTest summary info:
|
/test connector=connectors/source-elasticsearh
Build FailedTest summary info:
|
/test connector=connectors/source-cockroachdb
Build FailedTest summary info:
|
/test connector=connectors/source-mysql
Build PassedTest summary info:
|
/test connector=connectors/source-mssql
Build PassedTest summary info:
|
/test connector=connectors/source-oracle
Build PassedTest summary info:
|
/test connector=connectors/source-postgres
Build PassedTest summary info:
|
/test connector=connectors/source-redshift
Build PassedTest summary info:
|
/test connector=connectors/source-sftp
Build PassedTest summary info:
|
/test connector=connectors/source-snowflake
Build FailedTest summary info:
|
/test connector=connectors/source-tidb
Build PassedTest summary info:
|
@evantahler do I have to publish the connectors or only updating the |
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.
@evantahler I think you rather wanted to mention PR #21306 . The current PR is addressing source connectors only as the others are touching destinations. |
For the same reasons I detailed here I think it's safe to merge these changes without version bump / publish. |
|
|
What
Issue: https://github.com/airbytehq/airbyte-internal-issues/issues/2539
Some source connectors have
supportsNormalization
andsupportsDbt
fields.These field are useless for sources and are now defined in destination definition.
How
Remove these fields from the
spec.json
fileUpdate the
expected_spec.json
used in testing.