You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/15 16:16:00 UTC
[jira] [Updated] (ARROW-16521) [C++][R] Configure curl timeout policy for S3
[ https://issues.apache.org/jira/browse/ARROW-16521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARROW-16521:
-----------------------------------
Labels: good-first-issue good-second-issue pull-request-available (was: good-first-issue good-second-issue)
> [C++][R] Configure curl timeout policy for S3
> ---------------------------------------------
>
> Key: ARROW-16521
> URL: https://issues.apache.org/jira/browse/ARROW-16521
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Python, R
> Affects Versions: 7.0.0
> Reporter: Carl Boettiger
> Assignee: Ziheng Wang
> Priority: Major
> Labels: good-first-issue, good-second-issue, pull-request-available
> Fix For: 9.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Is it possible for the user to increase the timeout allowed on the curl settings when accessing S3 records? The default setting appears to be more aggressive than most other S3 clients I use, which means that I see a lot more failures on arrow-based operations than the other clients see. I'm not seeing how this can be increased though?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)