[DRILL-5040] Interrupted CTAS should not succeed & should not create physical file on disk

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.10.0
• Component/s: Execution - Flow
• Labels: ready-to-commit
• Assignee: Arina Ielchiieva
• Reporter: Khurram Faraaz
• Reviewer: Padma Penumarthy
• Created: 14/Nov/16 11:44
• Updated: 23/Mar/17 06:05
• Resolved: 12/Feb/17 23:13

Description

We should not allow CTAS to succeed (i.e create physical file on disk ) in the case where it was interrupted. (vis Ctrl-C)

Drill 1.9.0
git commit ID : db30854

Consider the below CTAS that was interrupted using Ctrl-C

0: jdbc:drill:schema=dfs.tmp> create table temp_t1 as select * from `twoKeyJsn.json`; 
[ issue Ctrl-C while the above CTAS is running ]
No rows affected (7.694 seconds)

I verified that physical file was created on disk, even though the above CTAS was Canceled

[root@centos-01 ~]# hadoop fs -ls /tmp/temp_t1*
-rwxr-xr-x   3 root root   36713198 2016-11-14 10:51 /tmp/temp_t1/0_0_0.parquet

We are able to do a select on the CTAS table (above) that was Canceled.

0: jdbc:drill:schema=dfs.tmp> select count(*) from temp_t1;
+----------+
|  EXPR$0  |
+----------+
| 3747840  |
+----------+
1 row selected (0.183 seconds)

Issue Links

• is duplicated by: DRILL-2293 CTAS does not clean up when it fails
• relates to: DRILL-4956 Temporary tables support
• links to: GitHub Pull Request #744