-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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 ClickHouse: bump dbt-clickhouse to v1.4.0 #23023
Conversation
/test connector=bases/base-normalization
Build FailedTest summary info:
|
@marcosmarxm @edgao integration tests for many unrelated destinations (BigQuery, DuckDB) failed. It's unlikely to be caused by the changes in the current PR. How should I proceed? |
/test connector=bases/base-normalization
Build FailedTest summary info:
|
/test connector=bases/base-normalization
Build FailedTest summary info:
|
@@ -476,7 +476,7 @@ def run_check_dbt_command(self, normalization_image: str, command: str, cwd: str | |||
""" | |||
Run dbt subprocess while checking and counting for "ERROR", "FAIL" or "WARNING" printed in its outputs | |||
""" | |||
if normalization_image.startswith("airbyte/normalization-oracle"): | |||
if normalization_image.startswith("airbyte/normalization-oracle") or normalization_image.startswith("airbyte/normalization-clickhouse"): |
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 two is fine to combine with the or
clause, but if we need to add another it might be worth switching to a collection
if any([normalization_image.startswith(x) for x in ["airbyte/normalization-oracle", "airbyte/normalization-clickhouse"]])
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.
once these live as connectors code it won't be a problem 😉 (but also yes. this entire section is kind of iffy. It kind of looks like recent dbt versions removed the --event-buffer-size
option entirely)
@grishick - base-normalization tests are passing on all destinations except bigquery, because of an upstream dependency bump. This PR (and your PR) both only touch clickhouse - I think we should be OK to publish skipping tests? the deps issue:
|
/publish connector=bases/base-normalization run-tests=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
running with run-tests=false. normalizatoin dockerfile is already at 0.2.26. |
FYI, this was merged because it qualifies as a P1 issue per this comment: https://github.com/airbytehq/oncall/issues/1474#issuecomment-1422777303 |
What
Updates DBT-clickhouse to v1.4.0
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 changes