-
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
Bigquery-denormalized fix integration tests #20640
Bigquery-denormalized fix integration tests #20640
Conversation
…o fix integration tests
/test connector=connectors/destination-bigquery-denormalized
Build PassedTest summary info:
|
Affected Connector ReportNOTE
|
Connector | Version | Changelog | Publish |
---|
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Destinations (1)
Connector | Version | Changelog | Publish |
---|---|---|---|
destination-bigquery-denormalized |
1.2.9 |
✅ | ✅ |
- 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/destination-bigquery-denormalized
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.
I think this is correct? but @pedroslopez can you confirm
also, isn't destination_definitions generated using the spec.json files? Shouldn't this have caused build failures, since ./gradlew build
would have generated a nonempty diff?
normalizationConfig: | ||
normalizationRepository: airbyte/normalization | ||
normalizationTag: 0.2.25 | ||
normalizationIntegrationType: bigquery |
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.
To confirm: are we saying here that this destination does not support normalization? (from the name -denormalized
i would assume so, but confirming 😄 )
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.
Yes, it was marked in spec.json
@edgao No, definitions are not generated. You may be thinking of destination_specs.yaml which are generated by running a spec command on the connector and saving the results. There's an upcoming ticket to remove supportsDbt and related fields from the spec and keep that information as part of the definitions only. I think this is it but there's not much info in it 😅 #18239 |
/approve-and-merge reason="Need to merge test fixes to unblock others. These changes affect only tests." |
What
in order to fix integration test,
spec.json
anddestination_definitions.yaml
should be consistent.old spec.json:
old destination_definitions.yaml:
result:
new spec.json:
destination_definitions.yaml:
How
Describe the solution
Recommended reading order
spec.json
destination_definitions.yaml
BigQueryDenormalizedDestinationAcceptanceTest.java