[ARROW-13370] [R] More special handling for known errors in arrow_eval

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: R
• External issue URL: https://github.com/apache/arrow/issues/29043
• Assignee: Unassigned
• Reporter: Neal Richardson
• Created: 17/Jul/21 21:23
• Updated: 11/Jan/23 08:32

Description

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).

Issue Links

• relates to: ARROW-15359 [R] Discussion: should we use {rlang} for condition handling?

Sub-Tasks

• [R] Investigate the use of rlang::abort() with the class arg: Closed
• [R] Investigate if an expansion of the {arrow} error classes is required: Closed
• [R] Surface error messages that do not contain the "not supported in Arrow" keywords: Closed
• [R] Update unit tests: Closed
• [R] Document updates in error-handling: Closed