[
https://issues.apache.org/jira/browse/ARROW-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912950#comment-16912950
]
Micah Kornfield commented on ARROW-6300:
----------------------------------------
It sounds like it makes sense, I think not just hiding it in the destructor
make sense (generally, I thought it was frowned upon to work that could fail in
the destructor anyways).
>> 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.
Are we writing temporary files and then moving them (i.e. letting the OS
cleanup the temporary file)?
> [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)
