drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Barclay (Drill) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-2560) JDBC execute calls return asynchronously for DDL statements
Date Tue, 18 Aug 2015 01:58:46 GMT

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

Daniel Barclay (Drill) updated DRILL-2560:
------------------------------------------
    Summary: JDBC execute calls return asynchronously for DDL statements  (was: JDBC execute
calls return asynchronously for DDLs)

> JDBC execute calls return asynchronously for DDL statements
> -----------------------------------------------------------
>
>                 Key: DRILL-2560
>                 URL: https://issues.apache.org/jira/browse/DRILL-2560
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 0.8.0
>            Reporter: Chris Westin
>            Assignee: Daniel Barclay (Drill)
>             Fix For: 1.3.0
>
>
> While working with TestViews, I noticed that JDBC's executeQuery() returns immediately
for drop view statements. For DDLs, users' expectation would be that the call would return
synchronously. The same would be true for execute(), and executeUpdate(), if used for DDLs.
This behavior is pretty typical for RDBMSs. This avoids the user having to consume the (non-)output
in order to wait for the statement to complete -- otherwise it will get cancelled when the
Statement is closed.



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

Mime
View raw message