[
https://issues.apache.org/jira/browse/ARROW-12509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489286#comment-17489286
]
Micah Kornfield edited comment on ARROW-12509 at 2/9/22, 6:52 AM:
------------------------------------------------------------------
Note about the use-case on the blocking issue. In the hadoop ecosystem GCS
tries to emulate renames by doing a copy and delete. The
[copy|https://github.com/GoogleCloudDataproc/hadoop-connectors/pull/622/files#diff-122b4a11389e8967ef7004ddf049fd1e7d688cf1c52fc16e61b0af2e60ed120dL1164]
use the if match feature) but I think this type of operation might be
expensive.
was (Author: emkornfield):
Note about the use-case on the blocking issue. In the hadoop ecosystem GCS
tries to emulate renames by doing a copy and delete. The
(https://github.com/GoogleCloudDataproc/hadoop-connectors/pull/622/files[copy
use the if match feature]) but I think this type of operation might be
expensive.
> [C++] More fine-grained control of file creation in filesystem layer
> --------------------------------------------------------------------
>
> Key: ARROW-12509
> URL: https://issues.apache.org/jira/browse/ARROW-12509
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Antoine Pitrou
> Assignee: Antoine Pitrou
> Priority: Major
>
> {{FileSystem::OpenOutputStream}} silently truncates an existing file.
> It would be better to give more control to the user. Ideally, one could
> choose between several options: "always overwrite and fail if doesn't exist",
> "overwrite if exists, otherwise create", "creates if doesn't exist, otherwise
> fails".
> One should research whether e.g. S3 supports such control.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
