You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Apache Arrow JIRA Bot (Jira)" <ji...@apache.org> on 2022/10/02 17:52:00 UTC

[jira] [Assigned] (ARROW-13370) [R] More special handling for known errors in arrow_eval

     [ https://issues.apache.org/jira/browse/ARROW-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Apache Arrow JIRA Bot reassigned ARROW-13370:
---------------------------------------------

    Assignee:     (was: Dragoș Moldovan-Grünfeld)

> [R] More special handling for known errors in arrow_eval
> --------------------------------------------------------
>
>                 Key: ARROW-13370
>                 URL: https://issues.apache.org/jira/browse/ARROW-13370
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: R
>            Reporter: Neal Richardson
>            Priority: Major
>
> *Proposed approach*:
> * Investigate the use of {{rlang::abort()}} with the class arg
> * Investigate if an expansion of the {{arrow}} error classes is required
> * Surface error messages that do not contain the "not supported in Arrow" keywords
> * Update unit tests
> * Document updates in error-handling
> *Original description*:
> We have special handling in arrow_eval that looks for the "not supported in Arrow" error, and when that's found it shows the error message rather than swallowing it in an "Expression not supported" message. But we have other error messages we raise in nse_funcs that are worth showing--bad input etc. Use a sentinel error message that we can also detect and subclass as "arrow-try-error" like the others, or (better) raise a classed exception (if that's supported in all versions of R we support). 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)