Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.8.0
-
None
Description
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.
Attachments
Issue Links
- incorporates
-
DRILL-3635 IllegalArgumentException - not a Parquet file (too small)
- Closed
- is related to
-
DRILL-3603 Document workaround for DRILL-2560 in JDBC Javadoc doc. (etc.)
- Open
- relates to
-
DRILL-3824 Cancelling the "refresh table metadata" command does not cancel it on the drillbit
- Open
-
DRILL-3160 Make JDBC Javadoc documentation available to users
- Resolved
-
DRILL-3778 Add rest of DRILL-3160 (making JDBC Javadoc available)
- Resolved
- requires
-
DRILL-3267 Distinguish non-query statements in SQL processing and RPC protocol
- Open
-
DRILL-3285 Split DrillCursor.next(), clean up DrillCursor for clarity
- Resolved