[
https://issues.apache.org/jira/browse/ARROW-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912119#comment-16912119
]
Antoine Pitrou commented on ARROW-6300:
---------------------------------------
> 1. What is the use-case for such a method? Are we expected to abort midway
> through?
In some cases yes. Suppose you're writing a file as part of a larger pipeline.
But another part of the pipeline fails, and you want to signal the stream that
it can abort its operations.
> 2. For regulard file systems, would it make sense to delete the underlying
> file (they both seem to be about clearing underlying resources?)
I don't think so. The aim is to clear any temporary runtime resources
associated to the stream. We don't claim that Abort() will rollback any
persistent changes.
Perhaps this is not necessary and we can just rely on the destructor, since C++
destruction is deterministic.
> [C++] Add io::OutputStream::Abort()
> -----------------------------------
>
> Key: ARROW-6300
> URL: https://issues.apache.org/jira/browse/ARROW-6300
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++
> Reporter: Antoine Pitrou
> Priority: Major
>
> This method would abort the current output stream without trying to flush or
> commit any pending internal data. This makes sense mostly for buffered
> streams. For other streams it could simply synonymous to Close().
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
