[R] Throw helpful errors on bad object types in dplyr expressions
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 4.3k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 88
Description
When users pass bad dots args to `mutate()` and other dplyr verbs (such that they could not succeed even if the data were pulled into R first), they should get immediate, informative errors.
An example:
```java
mtcars %>% Table$create() %>% mutate(c)
```
**Reporter**: [Ian Cook](https://issues.apache.org/jira/browse/ARROW-12093) / @ianmcook
#### PRs and other links:
- [GitHub Pull Request #9805](https://github.com/apache/arrow/pull/9805)
**Note**: *This issue was originally created as [ARROW-12093](https://issues.apache.org/jira/browse/ARROW-12093). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by reproducing the R example using Table$create() and mutate(c), then trace how dplyr expressions and dots arguments are handled for mutate() and other verbs. Done means bad object types that could not succeed after collecting into R fail immediately with helpful, informative errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100