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/25 02:29:00 UTC
[jira] [Closed] (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 closed FLINK-17878.
--------------------------------
Resolution: Fixed
master: e345d99a9e55a91d96fc5fc0e575ab7823f6fb74
release-1.11: ff3ea323c8d98e075a742afad6b08ec18a830046
> 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)