Canceling a (long-running) query

[ianmcook]

Canceling a (long-running) query

[ianmcook]

Thanks for asking about this. Cancelling queries is a tricky problem because of how the stack of packages that support implyr works. The odbc package, for example, runs C++ code that can't or doesn't check for interrupts from R.

There are possible workarounds for this, for example, we could implement an alternative version of the collect() function that would work asynchronously and would check often for interrupts or cancel commands.

Do these long waits typically happen after you've executed a collect() command? Or in some other situation?

[henningsway]

It depends. It does often happen after I sent a collect(), but also , when I work with a remote tbl, want to see the output of some sql-transformations and underestimated the time the computation of the preview takes. ;-)

I would guess that both cases happen about equally often. (Though for the second one, I could also try to develop on much smaller subset more often.)

[henningsway]

I think something similar has been implemented for sparklyr recently: https://blog.rstudio.com/2018/10/01/sparklyr-0-9/