Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.11.0
Description
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?
Attachments
Issue Links
- duplicates
-
FLINK-17885 StreamingFileCommitter watermark attribute is transient, this might be different with origin value
- Closed
- links to