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

Bowen Li updated FLINK-10168:
-----------------------------
    Description: 
Update: The motivation is 1) enabling users to set a read start position for 
files, so they can process files that are modified after a given timestamp 2) 
expose more file information to users and providing them with a more flexible 
file filter interface to define their own filtering rules

---------------

support filtering files by modified/created time in 
{{StreamExecutionEnvironment.readFile()}}

for example, in a source dir with lots of file, we only want to read files that 
is created or modified after a specific time.

This API can expose a generic filter function of files, and let users define 
filtering rules. Currently Flink only supports filtering files by path. What 
this means is that, currently the API is 
{{FileInputFormat.setFilesFilters(PathFiter)}} that takes only one file path 
filter. A more generic API that can take more filters can look like this 1) 
{{FileInputFormat.setFilesFilters(List (PathFiter, ModifiedTileFilter, ... ))}}

2) or {{FileInputFormat.setFilesFilters(FileFiter),}} and {{FileFilter}} 
exposes all file attributes that Flink's file system can provide, like path and 
modified time

I lean towards the 2nd option, because it gives users more flexibility to 
define complex filtering rules based on combinations of file attributes.

 

  was:
support filtering files by modified/created time in 
{{StreamExecutionEnvironment.readFile()}}

for example, in a source dir with lots of file, we only want to read files that 
is created or modified after a specific time.

This API can expose a generic filter function of files, and let users define 
filtering rules. Currently Flink only supports filtering files by path. What 
this means is that, currently the API is 
{{FileInputFormat.setFilesFilters(PathFiter)}} that takes only one file path 
filter. A more generic API that can take more filters can look like this 1) 
{{FileInputFormat.setFilesFilters(List (PathFiter, ModifiedTileFilter, ... ))}}

2) or {{FileInputFormat.setFilesFilters(FileFiter),}} and {{FileFilter}} 
exposes all file attributes that Flink's file system can provide, like path and 
modified time

I lean towards the 2nd option, because it gives users more flexibility to 
define complex filtering rules based on combinations of file attributes.

 


> support reading files whose modification time is after a given timestamp
> ------------------------------------------------------------------------
>
>                 Key: FLINK-10168
>                 URL: https://issues.apache.org/jira/browse/FLINK-10168
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API
>    Affects Versions: 1.6.0
>            Reporter: Bowen Li
>            Assignee: Bowen Li
>            Priority: Major
>             Fix For: 1.8.0
>
>
> Update: The motivation is 1) enabling users to set a read start position for 
> files, so they can process files that are modified after a given timestamp 2) 
> expose more file information to users and providing them with a more flexible 
> file filter interface to define their own filtering rules
> ---------------
> support filtering files by modified/created time in 
> {{StreamExecutionEnvironment.readFile()}}
> for example, in a source dir with lots of file, we only want to read files 
> that is created or modified after a specific time.
> This API can expose a generic filter function of files, and let users define 
> filtering rules. Currently Flink only supports filtering files by path. What 
> this means is that, currently the API is 
> {{FileInputFormat.setFilesFilters(PathFiter)}} that takes only one file path 
> filter. A more generic API that can take more filters can look like this 1) 
> {{FileInputFormat.setFilesFilters(List (PathFiter, ModifiedTileFilter, ... 
> ))}}
> 2) or {{FileInputFormat.setFilesFilters(FileFiter),}} and {{FileFilter}} 
> exposes all file attributes that Flink's file system can provide, like path 
> and modified time
> I lean towards the 2nd option, because it gives users more flexibility to 
> define complex filtering rules based on combinations of file attributes.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to