-
Notifications
You must be signed in to change notification settings - Fork 17.4k
Add durable execution to SnowflakeSqlApiOperator #69477
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
Open
amoghrajesh
wants to merge
4
commits into
apache:main
Choose a base branch
from
astronomer:snowflake-crash-recovery
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+407
−57
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c7cef50
Fix SnowflakeSqlApiOperator polling to avoid needless sleeps
amoghrajesh 092191c
Add durable execution to SnowflakeSqlApiOperator
amoghrajesh f0e0355
Merge branch 'main' into snowflake-crash-recovery
amoghrajesh a02ce7a
handling mypy
amoghrajesh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
On the failure path
query_idsis never pushed to xcom. When a statement errors,poll_on_queries()reports the error and this method raisesRuntimeErrorat line 567, before it reaches thisxcom_push. That is the case where the handles matter most, since you need them to look the failed statements up in Snowflake.The pre-PR non-deferrable path pushed
query_idsimmediately afterexecute_query(before the poll loop), so the handles were recorded even when a query failed. This moves the push after the loop, so a failure now loses them.Consider pushing the xcom near the top of
poll_until_complete(right afterself.query_ids = ..., before the poll loop) so it lands on both the fresh and reconnect paths and survives an error. Non-blocking.