-
Notifications
You must be signed in to change notification settings - Fork 66
Open
Description
Problem description
In FLIP-167, a new watermark API is introduced in both the new and old Sink API
We can
- Change our current watermark implementation in
SinkFunctionimplementation. We can get rid of the periodic checking per event and only propagate the watermark to Pravega in thewriteWatermarkcall. - For new Sink API, add the watermark propagation logic in the
SinkWriterand let user use anenableWatermarkPropagation(true)call to trigger in the builder.
Problem location
the new and old Sink API
Suggestions for an improvement
Reactions are currently unavailable