Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Some output sinks have a flush() method separate from write(...). Rather than flushing all writes, we can leave this up to the implementation, and have a default no-op Flush implementation. This came up during ARROW-404 (ran into test failure with unflushed writes, because the Java HDFS client does not auto-flush)
Attachments
Issue Links
- relates to
-
ARROW-404 [Python] Closing an HdfsClient while there are still open file handles results in a crash
- Resolved