You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Francis Chuang (JIRA)" <ji...@apache.org> on 2018/06/26 00:57:01 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 ]

Francis Chuang updated CALCITE-1350:
------------------------------------
    Fix Version/s:     (was: avatica-1.12.0)
                   avatica-1.13.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.13.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
(v7.6.3#76005)