-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Add Deferrable switch to SnowflakeSqlApiOperator #31596
Add Deferrable switch to SnowflakeSqlApiOperator #31596
Conversation
Co-authored-by: Tzu-ping Chung <[email protected]>
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.
lgtm
resp = await response.json() | ||
return self._process_response(status_code, resp) |
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 wonder if we should make the response body be fetched lazily, what could take a while (and might actually be the part worth deferring—not sure)
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.
@uranusjr I'm not sure I understand you completely, but based on what I got. The function get_sql_api_query_status_async
is called indirectly when we are polling for the status of the query within triggered. So deferring it would not be ideal, right?
Co-authored-by: Jed Cunningham <[email protected]>
Co-authored-by: Jed Cunningham <[email protected]>
Co-authored-by: Tzu-ping Chung <[email protected]>
Co-authored-by: Jed Cunningham <[email protected]>
07d3fae
to
b39b57b
Compare
I think you should rebase/solve conflicts on that one jsut to be sure. |
This PR donates the SnowflakeSqlApiOperator deferrable developed in astronomer-providers repo to Apache airflow.