-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeouts when running with paws.database 0.1.10 #132
Comments
Hi @davidski thanks for letting me know. Does this error happen with the DBI interface? Or is it just the dplyr interface? I will have a little look at paws.database to see what the change could be and how to fix it :) |
Thanks for the quick response! Yes, this problem occurs when making a DBI-style query as well. |
@davidski how long did this query run before it timed out? |
dbGetQuery breakdown:dbGetQuery calls the following noctua methods:
dbSendQuery calls:
dbStatistics calls:
dbFetch calls:
dbClearResult calls:
|
As the statistics of the query has been returned ( |
Thanks for diagnosing the bug, which we inappropriately introduced as a default timeout in the last release of |
@davidkretch thanks again. I will close this ticket. |
Issue Description
Under
noctua
1.10.0, going topaws.database
0.1.10 seems to cause curl timeouts when using the dplyr interface to queries.(Semi-)Reproducible Example
Generating a clean reprex is tricky, but I have a local query managed under
renv
that reliably replicates the problem. Here is a redacted query (hitting an Apache log store in parquet format) that demonstrates the problem:Error under paws.database 1.10.0
If left to run, the query goes through exponential back-off and eventually fails.
Running the same query under
paws.database
0.1.9 works without issue.noctua
1.9.1 also hits this problem, so this seems to be something in the interface withpaws
(or maybe even a problem withpaws
itself).Really appreciate the package. If there's a better way to help debug this, please let me know!
The text was updated successfully, but these errors were encountered: