[jira] [Updated] (FLINK-8599) Improve the failure behavior of the FileInputFormat for bad files

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot updated FLINK-8599:
----------------------------------
    Labels: pull-request-available  (was: )

> Improve the failure behavior of the FileInputFormat for bad files
> -----------------------------------------------------------------
>
>                 Key: FLINK-8599
>                 URL: https://issues.apache.org/jira/browse/FLINK-8599
>             Project: Flink
>          Issue Type: New Feature
>          Components: API / DataStream
>    Affects Versions: 1.3.2, 1.4.0
>            Reporter: Chengzhi Zhao
>            Priority: Major
>              Labels: pull-request-available
>
> So we have a s3 path that flink is monitoring that path to see new files available.
> {code:java}
> val avroInputStream_activity = env.readFile(format, path, FileProcessingMode.PROCESS_CONTINUOUSLY, 10000)  {code}
>  
> I am doing both internal and external check pointing and let's say there is a bad file (for example, a different schema been dropped in this folder) came to the path and flink will do several retries. I want to take those bad files and let the process continue. However, since the file path persist in the checkpoint, when I try to resume from external checkpoint, it threw the following error on no file been found.
>  
> {code:java}
> java.io.IOException: Error opening the Input Split s3a://myfile [0,904]: No such file or directory: s3a://myfile{code}
>  
> As [~fhueske@gmail.com] suggested, we could check if a path exists and before trying to read a file and ignore the input split instead of throwing an exception and causing a failure.
>  
> Also, I am thinking about add an error output for bad files as an option to users. So if there is any bad files exist we could move them in a separated path and do further analysis. 
>  
> Not sure how people feel about it, but I'd like to contribute on it if people think this can be an improvement. 



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