connection remaining open from databricks sql after timeout #13
Labels
bug
Something isn't working
Comments
avelino
added a commit
that referenced
this issue
Aug 1, 2024
we implemented it, but it was not being used it will not solve the issue of keeping the connection open described in issue #13, but it keeps the JDBC implementation organized Signed-off-by: Avelino <[email protected]>
avelino
added a commit
that referenced
this issue
Aug 9, 2024
we implemented it, but it was not being used it will not solve the issue of keeping the connection open described in issue #13, but it keeps the JDBC implementation organized Signed-off-by: Avelino <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When executing a query that takes a long time to run, there will come a point where Metabase will kill the query and send a "close" signal to Databricks SQL, but Databricks ignores "close" via JDBC.
proposed solution
Identify the
idof the query that received a timeout exception, perform the "close" (as done today) and make a request to the Databricks SQL API to kill the query.Databricks API: Cancel statement execution
The text was updated successfully, but these errors were encountered: