You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (Jira)" <ji...@apache.org> on 2021/12/11 17:32:00 UTC
[jira] [Updated] (CALCITE-1350) Avoid closeConnection when openConnection doesn't finish/succeed
[ https://issues.apache.org/jira/browse/CALCITE-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated CALCITE-1350:
--------------------------------
Fix Version/s: avatica-1.21.0
(was: avatica-1.20.0)
> Avoid closeConnection when openConnection doesn't finish/succeed
> ----------------------------------------------------------------
>
> Key: CALCITE-1350
> URL: https://issues.apache.org/jira/browse/CALCITE-1350
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
> Fix For: avatica-1.21.0
>
>
> I've noticed during testing of Avatica, often times when SPNEGO authentication is misconfigured, the client will get stuck in openConnection().
> If we consider sqlline and the user control-C's it, sqlline will try to close the driver as well which would do a closeConnection() (which would also obviously fail).
> I believe we should be able to short-circuit the the closeConnection() when we know that the openConnection() didn't succeed properly.
> Another scenario is when the Avatica server is down. openConnection will fail, but we'll still attempt the closeConnection on exit.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)