Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 1 Nov 2016 11:48:59 +0000 (UTC)
From: "Takuya Kojima (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13012747.1476672233000.143276.1478000939492@Atlassian.JIRA>
In-Reply-To: <JIRA.13012747.1476672233000@Atlassian.JIRA>
References: <JIRA.13012747.1476672233000@Atlassian.JIRA> <JIRA.13012747.1476672233245@arcas>
Subject: [jira] [Updated] (DRILL-4948) Re-connection without explicit new
 connection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 01 Nov 2016 11:49:02 -0000


     [ https://issues.apache.org/jira/browse/DRILL-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Takuya Kojima updated DRILL-4948:
---------------------------------
    Affects Version/s:     (was: Future)
        Fix Version/s: Future

> Re-connection without explicit new connection
> ---------------------------------------------
>
>                 Key: DRILL-4948
>                 URL: https://issues.apache.org/jira/browse/DRILL-4948
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Client - JDBC
>            Reporter: Takuya Kojima
>            Priority: Minor
>             Fix For: Future
>
>
> Current JDBC driver's behavior is basically need to abort old connection and create new one when lost the connection.
> Re-connection by the application is not bad, but traditional DB products(e.g. Postgres, Vertica) JDBC driver can handle it without explicit re-connection.
> So, it would be great enhancement for new comer from another DB products world.
> See also this closed bug ticket: #4876


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)