Repository navigation
Edgao/component upsert tests/connectors - #68186
Conversation
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. Helpful Resources
PR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
|
|
|
34fc6e7 to
8d94d4a
Compare
7f417e8 to
3d46ccc
Compare
…psert_tests/cdk # Conflicts: # airbyte-cdk/bulk/core/load/src/testFixtures/kotlin/io/airbyte/cdk/load/component/TableOperationsFixtures.kt
…upsert_tests/connectors
# Conflicts: # airbyte-cdk/bulk/core/load/src/testFixtures/kotlin/io/airbyte/cdk/load/component/TableOperationsFixtures.kt # airbyte-cdk/bulk/core/load/src/testFixtures/kotlin/io/airbyte/cdk/load/component/TableOperationsSuite.kt # airbyte-cdk/bulk/core/load/src/testFixtures/kotlin/io/airbyte/cdk/load/component/TableOperationsTestHarness.kt # airbyte-integrations/connectors/destination-clickhouse/gradle.properties # airbyte-integrations/connectors/destination-snowflake/gradle.properties # airbyte-integrations/connectors/destination-snowflake/src/main/kotlin/io/airbyte/integrations/destination/snowflake/client/SnowflakeAirbyteClient.kt
…upsert_tests/connectors
…upsert_tests/connectors
| # ClickHouse | ||
|
|
||
| A fresh implementation of ClickHouse leveraging our new CDK. | ||
| A fresh implementation of ClickHouse leveraging our new CDK. |
There was a problem hiding this comment.
[Google.We] Try to avoid using first-person plural like 'our'.
There was a problem hiding this comment.
[markdownlint-fix] reported by reviewdog 🐶
airbyte/docs/integrations/destinations/clickhouse.md
Lines 6 to 9 in 846d001
|
Note Detected that there are differences in the Gradle dependencies. |
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit 846d001. |
What
Connectors half of part 2 of https://github.com/airbytehq/airbyte-internal-issues/issues/14865. Branched from #68185.
How
Mostly just minor tweaks. Crucially, make snowflake's readTable method read timestamptz/array/object/variant in the way that the expected records expect.
Technically: we could make the snowflake tests declare a different set of expected records? But that feels really annoying, given that I want to change the input records at some point https://github.com/airbytehq/airbyte-internal-issues/issues/14910
(the readTable changes also just seem pretty reasonable, i.e. read an iso8601 timestamp instead of whatever snowflake does by default; read unstructured types into a map/list/etc. instead of leaving them as string)
Review guide
As usual, review each commit in sequence.
Can this PR be safely reverted and rolled back?