Search before asking
Motivation
Currently, Fluss Flink connector supports table-level watermark via WATERMARK FOR in DDL,
which is pushed down through Flink's SupportsWatermarkPushDown interface. However, there are
two common scenarios that are not well supported:
- Legacy tables that already have a table-level
WATERMARK definition but users want to
disable it at query time without altering the table schema.
- Ad-hoc watermark override where users want to specify a different watermark column or
delay at query time via SQL hints, without modifying the table definition.
Solution
No response
Anything else?
No response
Willingness to contribute
Search before asking
Motivation
Currently, Fluss Flink connector supports table-level watermark via
WATERMARK FORin DDL,which is pushed down through Flink's
SupportsWatermarkPushDowninterface. However, there aretwo common scenarios that are not well supported:
WATERMARKdefinition but users want todisable it at query time without altering the table schema.
delay at query time via SQL hints, without modifying the table definition.
Solution
No response
Anything else?
No response
Willingness to contribute