-
Notifications
You must be signed in to change notification settings - Fork 175
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
Unable to connect to bigqueyr table in dev version #1326
Comments
I've been seeing this error too using the AlloUs Research program's workbench. The error only seems to occur when no other SQL is added to the query at least in this case. I"ve tried with CRAN and dev versions of dplyr/dbplyr. Thanks! For example, this would not work:
This works:
Here's the error from our actual db:
|
Looks like it was reported in r-dbi/bigrquery#509 and fixed in r-dbi/bigrquery#512 |
Apologies.. what is the status of this/final solution? I am using bigrquery_1.4.2 dbplyr_2.4.0 dplyr_1.1.3 and getting the error |
Yes, that actually appears to be a different problem, despite the similar error. I am working on bigrquery for a bit and will hopefully have a fix soon. |
That would be great. Thank you. |
@paulcbauer it's fixed |
It works. Thank you! |
This is not yet fixed in the version(s) of the packages on CRAN, correct @hadley? I am seeing the same issue as @paulcbauer.
|
Not on CRAN yet I think but you can install the development versions which worked for me:
|
Thanks. That works for me as well. However, I need it in a production app, where I don't want to use development versions of packages. Alas, I will (need to) wait. |
Hi, not sure if the issue is caused by #1287 or something else but I am unable to connect to bigquery tables using the latest dev version of the package.
Using a public bigquery dataset, I get the following error when running the tbl command.
Error in strsplit(name, ".", fixed = TRUE) : non-character argument
Package versions are:
dbplyr: 2.3.2.9000
dplyr: 1.1.2
DBI: 1.1.3
The text was updated successfully, but these errors were encountered: