Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Cannot Reproduce
-
Impala 2.2
-
None
-
2.2 pre-release
Description
I cancelled an INSERT statement when I realized it was going to take a long time and not match anything.
[localhost:21000] > insert into partitioned_text (x, y, s) partition (year=2014,month=1,day=1) select id, val, name from oreilly.sample_data
> where zerofill like '20140101%' limit 1e6;
^C Cancelling Query
Application Exception : Default TException.
Subsequent INSERT statements did not show any 'Inserted NNN rows' messages, so I assumed they were unsuccessful.
[localhost:21000] > insert into partitioned_text (x, y, s) partition (year=2014,month=1,day=1) select id, val, name from oreilly.sample_data where id = 20140101 limit 1e6; [localhost:21000] > insert into partitioned_text (x, y, s) partition (year=2014,month=1,day=1) select id, val, name from oreilly.normalized_parquet where id between 1 and 1000000;
However, they apparently did succeed and inserted the expected number of rows.
[localhost:21000] > select count(*) from partitioned_text; +----------+ | count(*) | +----------+ | 1000001 | +----------+
My hypothesis is that the error handler in impala-shell turned off some messaging flag when I cancelled the query via Ctrl-C, and this flag remained off afterwards.