Closed motykatomasz closed 3 days ago
From Snowflake support for I think is the same issue:
Hi Greg, Thanks for your patience. It seems that we have identified the root cause of this and fixed it around four hours ago. Please continue to monitor this and let us know if the issue is resolved.
Yup, seems it is fixed.
Seems that the issue still persists.
hello - unfortunately we indeed had an issue for some customers where the queries executed asynchronously did not appear in the Query History. This is coming from the Snowflake backend (thus, not the client-side PythonConnector, this library) and supposed to be resolved.
If any of you still experiences this weird issue, we will need details, most of all queryIds which were launched recently (past 1-2 days) and still are affected.
Please, could you share either privately provide those examples to Snowflake Support, or here?
@sfc-gh-dszmolka We opened a case in Snowflake Support but we haven't received any new updates there yet. Do you know what's the status for resolving this issue? Unfortunately it sill persists.
i'm sorry to hear that you're not getting responses in a timely manner - but still the best way is to ask for updates in the same case you have with support. We have procedures, metrics, etc. tied to the support cases which simply don't exist out here in Github issues.
To my best knowledge is that issue supposed to be resolved, but unfortunately some of our customers see it. My colleagues in the relevant dev teams of Snowflake engine (thus, not the driver library here) are investigating and looking for new examples, queryIds that seems to be 'missing'. If you have them, please do share with your support engineer who is handling the case. You also have the option to escalate the support case if the issue is getting more serious for you.
short update: my dev colleagues taking care of the Snowflake engine seems to have found a way to mitigate this issue; it's an account wide internal setting which is not accessible from the customer side.
If you already have a case open and still seeing this issue, please refer to SNOW-1644152
for your support engineer so they could proceed with the mitigation. If you're just finding this thread because being affected, please raise a case with Snowflake Support and reference SNOW-1644152
.
Since the issue seems to turn out to be unrelated to Snowflake's PythonConnector (this library, in which this issue has been raised originally), please work with Snowflake Support for the mitigation and official root cause analysis. Thank you and again apologies for any inconvenience caused by this unexpected misbehaviour.
editing this comment to add a fresh information just becoming available to me; apparently the mitigation will be deployed system-wide with Snowflake version 8.35, planned to be deployed on week of 16 September 2024. (you can check current Snowflake engine version with select current_version()
)
Marking this issue as closed for now as it is unrelated to PythonConnector.
Python version
3.11.9
Operating system and processor architecture
macOS-14.6.1-arm64-arm-64bit
Installed packages
What did you do?
We had a sudden problem in a project with executing async queries, so I tested it on the simplest setup:
and indeed, it turns out that the query is not being executed. However, if I try to execute the query synchronously it runs just fine:
What did you expect to see?
I'd expect to see the result of the async query and to see this particular query in the query history in the snowflake monitoring UI.
Can you set logging to DEBUG and collect the logs?