You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current setup, we cannot run multiple queries even though the execute_async returns control to the user immediately. We need the execute_async to return a future or an id which the user can use to specify the query they want o spin on.
Adding support for this workflow using the following API changes.
.execute_async() - returns a future
.fetch_all(future) - returns all the rows
The text was updated successfully, but these errors were encountered:
After my refactoring in Feb 23, we should be able to support two concurrent queries from two terminal clients. I think I left this message for two concurrent queries from a same terminal client. Can you please check?
In the current setup, we cannot run multiple queries even though the
execute_async
returns control to the user immediately. We need theexecute_async
to return a future or an id which the user can use to specify the query they want o spin on.Adding support for this workflow using the following API changes.
.execute_async()
- returns a future.fetch_all(future)
- returns all the rowsThe text was updated successfully, but these errors were encountered: