[ 
https://issues.apache.org/jira/browse/FLINK-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383441#comment-16383441
 ] 

Piotr Nowojski commented on FLINK-8794:
---------------------------------------

The temporary data is already separated from the final output - it's in 
different files. If we allow for different directory that should be already 
enough.

Besides, writing to local disks would decrease performance, since you would 
need to write the same data twice (first locally then copy remotely, which is 
unnecessary, while moving files between directories is cheap) and stil 
"pending" files would have to be copied to remote location, since in some cases 
"pending" files are committed during recovery. Thus it wouldn't solve your 
problem.

> When using BucketingSink, it happens that one of the files is always in the 
> [.in-progress] state
> ------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-8794
>                 URL: https://issues.apache.org/jira/browse/FLINK-8794
>             Project: Flink
>          Issue Type: Bug
>          Components: filesystem-connector
>    Affects Versions: 1.4.0, 1.4.1
>            Reporter: yanxiaobin
>            Priority: Major
>
> When using BucketingSink, it happens that one of the files is always in the 
> [.in-progress] state. And this state has never changed after that.  The 
> underlying use of S3 as storage.
>  
> {code:java}
> // code placeholder
> {code}
> 2018-02-28 11:58:42  147341619 {color:#d04437}_part-28-0.in-progress{color}
> 2018-02-28 12:06:27  147315059 part-0-0
> 2018-02-28 12:06:27  147462359 part-1-0
> 2018-02-28 12:06:27  147316006 part-10-0
> 2018-02-28 12:06:28  147349854 part-100-0
> 2018-02-28 12:06:27  147421625 part-101-0
> 2018-02-28 12:06:27  147443830 part-102-0
> 2018-02-28 12:06:27  147372801 part-103-0
> 2018-02-28 12:06:27  147343670 part-104-0
> ......



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

Reply via email to