Skip to content
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

Release 0.2.2 #39

Merged
merged 4 commits into from
Apr 5, 2024
Merged

Release 0.2.2 #39

merged 4 commits into from
Apr 5, 2024

Conversation

istreeter
Copy link
Collaborator

No description provided.

Previously we used the `TIMESTAMP` column type. In Snowflake, this is
_probably_ an alias for `TIMESTAMP_NTZ`, but actually it depends on
whether the account owner has change the default of the
`TIMESTAMP_TYPE_MAPPING` session parameter.

We should pick a concrete timestamp type and use it explicitly for all
new tables. This will prevent future confusion where we are not 100%
sure what timestamp got used when creating the table.

This change was supposed to happen in the first release, but it got
overlooked.
Before this PR, the loader would crash immediately if the events table
is missing a required column like `load_tstamp`. It is better if the
loader stays alive long enough to send an informative message to the
monitoring webhook.
Snowflake responds with a 4xx response code for various reasons when
opening a channel:

- User does not have permissions (403)
- This table type does not support channels (400)
- There are probably others I have not seen yet!

Before this PR, if we treated the 403 as a setup error, but actually all
4xxs are probably setup errors. We should treat them gracefully by
staying alive and sending an informative message to the monitoring
webhook.
@istreeter istreeter merged commit 5c37862 into main Apr 5, 2024
6 checks passed
@istreeter istreeter deleted the release-0.2.2 branch April 5, 2024 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants