swuferhong opened a new issue, #3265: URL: https://github.com/apache/fluss/issues/3265
### 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! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
