[jira] [Resolved] (ARROW-11718) [Rust] IPC writers shouldn't implicitly finish on drop

["Neville Dipale (Jira)" <ji...@apache.org>]

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

Neville Dipale resolved ARROW-11718.
------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 9536
[https://github.com/apache/arrow/pull/9536]

> [Rust] IPC writers shouldn't implicitly finish on drop
> ------------------------------------------------------
>
>                 Key: ARROW-11718
>                 URL: https://issues.apache.org/jira/browse/ARROW-11718
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Rust
>    Affects Versions: 3.0.0
>            Reporter: Steven Fackler
>            Assignee: Steven Fackler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The Rust IPC writer types have a destructor that automatically writes the footer if necessary. This is not ideal, though, since it can hide errors. For example, if a web server is streaming data to a client in the Arrow IPC format and it encounters an internal error trying to generate the next batch, the outbound stream will appear valid to the client as the footer will automatically be written out but some amount of data will actually be missing. If the footer was not automatically written, the client would properly detect the truncation.
> For reference, the C++ implementation does not attempt to write the footer implicitly on drop.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)