[ https://issues.apache.org/jira/browse/DRILL-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862161#comment-15862161 ]
ASF GitHub Bot commented on DRILL-5040: --------------------------------------- Github user amansinha100 commented on the issue: https://github.com/apache/drill/pull/744 +1 > Interrupted CTAS should not succeed & should not create physical file on disk > ----------------------------------------------------------------------------- > > Key: DRILL-5040 > URL: https://issues.apache.org/jira/browse/DRILL-5040 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Flow > Affects Versions: 1.9.0 > Reporter: Khurram Faraaz > Assignee: Arina Ielchiieva > Labels: ready-to-commit > Fix For: 1.10.0 > > > 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 > {noformat} > 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) > {noformat} > I verified that physical file was created on disk, even though the above CTAS > was Canceled > {noformat} > [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 > {noformat} > We are able to do a select on the CTAS table (above) that was Canceled. > {noformat} > 0: jdbc:drill:schema=dfs.tmp> select count(*) from temp_t1; > +----------+ > | EXPR$0 | > +----------+ > | 3747840 | > +----------+ > 1 row selected (0.183 seconds) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)