[DRILL-2884] Have cancel() cause "query canceled" rather than just "ResultSet closed"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Assignee: Daniel Barclay
• Reporter: Daniel Barclay
• Created: 27/Apr/15 20:00
• Updated: 01/Jul/16 18:33
• Resolved: 06/May/15 21:54

Description

After Statement.cancel() is called for a SQL statement's execution, a subsequent call to a method on the ResultSet for that execution yields a "ResultSet already closed" exception. (This isn't fully implemented yet, but it is for, e.g., next().)

A call to cancel() should result in an explicit "execution canceled" exception rather than the usual "already closed" exception (so that it doesn't seem like a Drill programming error rather an expected result of canceling).

Issue Links

• relates to: CALCITE-872 Add support for aborting the query optimization process
• supercedes: DRILL-2837 Resolve what Statement.cancel() really should do