Destination Snowflake: Write extracted_at in UTC

[edgao]

Hopefully most changes are reasonably self-explanatory, but a few callouts:

• SnowflakeDestinationHandler now upcases the database name in the constructor, before assigning it to the field. This is because in the rest of the connector, we never enquote the database name - so when we query information_schema, we need to always upcase it.
• There's a new test case that runs a sync with destination-snowflake:3.5.11, i.e. a version that still wrote extracted_at in the user local timezone instead of UTC. I added some ltz_*_expectedrecords_*.jsonl files to verify that that sync behaved as expected - not strictly necessary, but it's nice to have a baseline assertion that the known-bad sync behaved in the way that we expect.
• All the other jsonl changes are exactly what you'd expect, i.e. switching extracted_at from -08:00 to Z.

We are not migrating existing timestamps in raw tables or final tables, instead we are relying on timestamp arithmetic to always force normalize it to UTC as below. Also as part of this PR, we are removing the optimization to use _airbyte_extracted_at > [a very old value] because of using the following conversion, that query became slow.

TIMESTAMPADD(
  HOUR,
  EXTRACT(TIMEZONE_HOUR from "_airbyte_extracted_at"),
  TIMESTAMPADD(
    MINUTE,
    EXTRACT(TIMEZONE_MINUTE from "_airbyte_extracted_at"),
    CONVERT_TIMEZONE('UTC', "_airbyte_extracted_at")
  ))

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Mar 6, 2024 3:40pm

[edgao]

• Destination Snowflake: Move legacy migrators to new framework #35644
• Java destinations: Move old dv2 migrators to new framework #35597
• Destination Snowflake: Write extracted_at in UTC #35308 👈
• Java CDK: Staging destinations include timezone in extracted_at in CSV file #35313 : 3 other dependent PRs (#35315 , #35316 , #35528 )
• DV2 destinations: Build DestinationState / Migration framework #35303
• DV2 TyperDeduper: Extract migrations to separate method #35376
• Destinations CDK: Refactor T+D to gather required world state upfront #35342 : 3 other dependent PRs (#35354 , #35385 , #35456 )
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @edgao and the rest of your teammates on Graphite

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.