-
Notifications
You must be signed in to change notification settings - Fork 104
Error in new get_async_execution_result() function in 3.7.0 #485
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
Comments
I'm also getting this error using the same function / following the example in https://github.com/databricks/databricks-sql-python/blob/main/tests/e2e/test_driver.py#L180-L199 |
@jprakash-db any idea why this occurs, is the fix related to https://github.com/databricks/databricks-sql-python/pull/480/files? |
@jprakash-db I am still getting this error in 3.7.2 and 4.0.0. Can't run async due to this. |
@hayescode The issue is that for very small/quick executing queries where results can be quickly served there is no state left on the server side. For queries that run for a long time as in |
@hayescode We have raised the fix in the new version of the PySQL Connector v3.7.3 |
@jprakash-db tested and working now. Thank you very much! |
cc @deeksha-db |
It seems the requested async support has been added in #463 however I get errors in the new
get_async_execution_result()
method which seems necessary.Sync (works)
Async (error)
Async Error:
The text was updated successfully, but these errors were encountered: