[jira] [Updated] (ARROW-17355) [R] Refactor the handle_* utility functions for a better dev experience

2022-09-02 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated ARROW-17355:
---
Labels: pull-request-available  (was: )

> [R] Refactor the handle_* utility functions for a better dev experience
> ---
>
> Key: ARROW-17355
> URL: https://issues.apache.org/jira/browse/ARROW-17355
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: R
>Reporter: Nicola Crane
>Assignee: Nicola Crane
>Priority: Major
>  Labels: pull-request-available
> Fix For: 10.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> In ARROW-15260, the utility functions for handling different kinds of reading 
> errors (handle_parquet_io_error, handle_csv_read_error, and 
> handle_augmented_field_misuse) were refactored so that multiple ones could be 
> chained together. An issue with this is that other errors may be swallowed if 
> they're used without any errors that they don't capture being raised manually 
> afterwards.  We should update the code to prevent this from being possible.



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


[jira] [Updated] (ARROW-17355) [R] Refactor the handle_* utility functions for a better dev experience

2022-08-11 Thread Nicola Crane (Jira)


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

Nicola Crane updated ARROW-17355:
-
Fix Version/s: 10.0.0

> [R] Refactor the handle_* utility functions for a better dev experience
> ---
>
> Key: ARROW-17355
> URL: https://issues.apache.org/jira/browse/ARROW-17355
> Project: Apache Arrow
>  Issue Type: Improvement
>  Components: R
>Reporter: Nicola Crane
>Priority: Major
> Fix For: 10.0.0
>
>
> In ARROW-15260, the utility functions for handling different kinds of reading 
> errors (handle_parquet_io_error, handle_csv_read_error, and 
> handle_augmented_field_misuse) were refactored so that multiple ones could be 
> chained together. An issue with this is that other errors may be swallowed if 
> they're used without any errors that they don't capture being raised manually 
> afterwards.  We should update the code to prevent this from being possible.



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