The GitHub Actions job "Nightly (beta)" on flink.git/release-2.4 has succeeded.
Run started by GitHub user github-actions[bot] (triggered by 
github-actions[bot]).

Head commit for run:
0d2200fad459b0c84485d803a177d5f728654915 / Sepuri Sai Krishna 
<[email protected]>
[FLINK-40924][table-planner] Enforce require-on-conflict under 
upsert-materialize FORCE (#29637)

The ON CONFLICT requirement was validated inside the AUTO branch of
analyzeUpsertMaterializeStrategy, so setting
table.exec.sink.upsert-materialize to FORCE skipped it and the query
planned even though its upsert key differs from the sink's primary key
and no ON CONFLICT clause was given.

FORCE adds the sink upsert materializer, and the materializer is what
applies the conflict strategy, so the clause does take effect under
FORCE. The check that already runs under AUTO now runs there too, with
the same condition.

NONE keeps its current behaviour on purpose. It removes the
materializer, so nothing is left to apply a conflict strategy and the
clause would have no effect. Opting out that way is documented in
docs/content/docs/sql/reference/dml/insert.md.

Generated-by: Claude Code (Opus 5)

Report URL: https://github.com/apache/flink/actions/runs/40803859897

With regards,
GitHub Actions via GitBox

Reply via email to