-
Notifications
You must be signed in to change notification settings - Fork 56
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
Using arrow results in error "not really a table object" #473
Comments
Thanks for reporting this and providing a lot of details! This is definitely not right and requires a fix. |
FWIW I see this more of a feature request than a bug. Think of arrow as another backend. I think the error message is informative (while not perfect). An As a first suggestion it would be great to have the documentation of the supported backends in a more prominent location (e.g. a paragraph in the {pagedown} site). A second suggestion: maybe, in a first instance, error with a clear message that arrow tables (or datasets, etc.) are not (yet) supported and have a follow-up issue to implement such support arrow inputs? (I have done some work on {arrow} in the past and I think this might not be a trivial endeavour). (by the way, thanks a lot for the great package and for the R in Pharma workshop) |
Prework
Description
When interrogating an agent that is an arrow object, I get the following error:
The 'table' in this validation step is not really a table object.
When I convert the arrow dataset to a data.frame first, pointblank works as expected
Reproducible example
Created on 2023-04-17 with reprex v2.0.2
Session info
The text was updated successfully, but these errors were encountered: