apache / apache/fluss

[flink] Support hint-based watermark configuration for Flink connector

Open
#3,265 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
2.1k
Forks
625
Avg merge
3d 14h
Merged PRs (30d)
97

Description

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.

### 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:

1. **Legacy tables** that already have a table-level `WATERMARK` definition but users want to
disable it at query time without altering the table schema.
2. **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

- [x] I'm willing to submit a PR!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the Fluss Flink connector implementation of Flink's SupportsWatermarkPushDown interface and its SQL hint handling. Trace how table-level WATERMARK definitions reach the connector, then define and test the expected behavior for disabling an existing watermark and overriding its column or delay through a query hint.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.