[
https://issues.apache.org/jira/browse/DRILL-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694019#comment-14694019
]
Deneche A. Hakim edited comment on DRILL-2560 at 8/13/15 9:10 PM:
------------------------------------------------------------------
We may be able to "force" executeQuery() to wait until a DDL finishes executing
by holding on returning the very first batch (fast schema), on the server side.
This may not work for all DDL's though
was (Author: adeneche):
We may be able to "force" executeQuery() to wait until a DDL finishes executing
by holding on returning the very first batch (fast schema), on the server side.
> JDBC execute calls return asynchronously for DDLs
> -------------------------------------------------
>
> 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)
