You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2020/05/22 13:51:00 UTC

[jira] [Updated] (FLINK-17878) Transient watermark attribute should be initial at runtime in streaming file operators

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

Jingsong Lee updated FLINK-17878:
---------------------------------
    Summary: Transient watermark attribute should be initial at runtime in streaming file operators  (was: StreamingFileWriter watermark attribute is transient, this might be different with origin value)

> Transient watermark attribute should be initial at runtime in streaming file operators
> --------------------------------------------------------------------------------------
>
>                 Key: FLINK-17878
>                 URL: https://issues.apache.org/jira/browse/FLINK-17878
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / FileSystem
>    Affects Versions: 1.11.0
>            Reporter: xiaogang zhou
>            Assignee: xiaogang zhou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>
> StreamingFileWriter has a 
> private transient long currentWatermark = Long.MIN_VALUE;
>  
> in case developer wants to create a custom bucket assigner, it will receive a currentWatermark as 0, this might be conflict with the original flink approach to handle a min_long.
>  
> should we remove the transient key word?
>  



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