[
https://issues.apache.org/jira/browse/FLINK-40987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo de Morais updated FLINK-40987:
--------------------------------------
Summary: Allow overriding a table's watermark per table reference via
OPTIONS hint (was: Allow overriding or disabling a table's watermark per table
reference via OPTIONS hint)
> Allow overriding a table's watermark per table reference via OPTIONS hint
> -------------------------------------------------------------------------
>
> Key: FLINK-40987
> URL: https://issues.apache.org/jira/browse/FLINK-40987
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Gustavo de Morais
> Priority: Major
>
> A table's watermark definition can only be changed through DDL (ALTER TABLE
> ... MODIFY/DROP WATERMARK, or CREATE TABLE ... LIKE), which affects every
> query on that table or requires a second table.
> The OPTIONS hint already allows tuning watermark emission per table reference
> (scan.watermark.emit.strategy, idle-timeout, alignment; FLIP-296). It cannot
> change the delay or turn the watermark off.
> Idea: two more options handled by the planner, for example:
>
> {code:java}
> SELECT * FROM orders /*+ OPTIONS('scan.watermark.delay' = '1 h') */;
> SELECT * FROM orders /*+ OPTIONS('scan.watermark.enabled' = 'false') */;{code}
>
> This adds no new semantics. The result is the same as MODIFY/DROP WATERMARK,
> scoped to one table reference in one statement. Changing the watermark column
> is out of scope.
> Motivation: connectors are starting to implement this themselves
> ([apache/fluss#3265|https://github.com/apache/fluss/pull/3266]), outside the
> planner.
> This ticket is to collect feedback on the idea and scope. Option names are
> placeholders.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
