You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Krisztian Szucs (Jira)" <ji...@apache.org> on 2020/01/25 17:00:00 UTC
[jira] [Comment Edited] (ARROW-7673) [C++][Dataset] Revisit File
discovery failure mode
[ https://issues.apache.org/jira/browse/ARROW-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023602#comment-17023602 ]
Krisztian Szucs edited comment on ARROW-7673 at 1/25/20 4:59 PM:
-----------------------------------------------------------------
[~fsaintjacques] So in 0.16 we plan to provide best effort readers, and aiming this ticket to 1.0.0, right?
was (Author: kszucs):
So in 0.16 we plan to provide best effort readers, and aiming this ticket to 1.0.0, right?
> [C++][Dataset] Revisit File discovery failure mode
> --------------------------------------------------
>
> Key: ARROW-7673
> URL: https://issues.apache.org/jira/browse/ARROW-7673
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++ - Dataset
> Reporter: Francois Saint-Jacques
> Priority: Major
>
> Currently, the default `FileSystemFactoryOptions::exclude_invalid_files` will silently ignore unsupported files (either IO error, not of the valid format, corruption, missing compression codecs, etc...) when creating a `FileSystemSource`.
> We should change this behavior to propagate an error in the Inspect/Finish calls by default and allow the user to toggle `exclude_invalid_files`. The error should contain at least the file path and a decipherable error (if possible).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)