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
Currently, a race is possible when you try to abort a query, but query finishes between get_state and abort:
>>> client.get_query('8afed27-c66b620d-f4e2d5dc-89661f2b', attributes=["state"])
{'state': 'completed'}
>>> client.abort_query('8afed27-c66b620d-f4e2d5dc-89661f2b')
Traceback (most recent call last):
# ...
params {
"suppress_transaction_coordinator_sync": false,
"query_id": "8afed27-c66b620d-f4e2d5dc-89661f2b",
"stage": "production"
}
transparent True
Query 8afed27-c66b620d-f4e2d5dc-89661f2b not found or is not running
Something like ignore_non_running_query will be very convenient since 99.9% of the time you don't care about the result of the query when you decide to call abort.
The text was updated successfully, but these errors were encountered:
Currently, a race is possible when you try to abort a query, but query finishes between
get_state
andabort
:Something like
ignore_non_running_query
will be very convenient since 99.9% of the time you don't care about the result of the query when you decide to callabort
.The text was updated successfully, but these errors were encountered: