You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Chris Westin (JIRA)" <ji...@apache.org> on 2015/03/25 18:40:53 UTC

[jira] [Created] (DRILL-2560) JDBC execute calls return asynchronously for DDLs

Chris Westin created DRILL-2560:
-----------------------------------

             Summary: 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)


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)