[
https://issues.apache.org/jira/browse/FLINK-40324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102095#comment-18102095
]
Gustavo de Morais commented on FLINK-40324:
-------------------------------------------
Fixed in master: 5d91e07c8f2cfc3b4d0e779748e08311ea306bd3
> Append-only should stay unmaterialized without an ON CONFLICT clause
> --------------------------------------------------------------------
>
> Key: FLINK-40324
> URL: https://issues.apache.org/jira/browse/FLINK-40324
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 2.3.0
> Reporter: Gustavo de Morais
> Assignee: Gustavo de Morais
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> FLIP-558 dropped the inputInsertOnly guard in apache Flink, so insert-only
> input into a sink with a primary key now gains a SinkUpsertMaterializer and a
> keyed shuffle it never had. Reachable under upsert-materialize=AUTO with
> require-on-conflict=false, and under FORCE regardless. Released in 2.3.0, and
> require-on-conflict is documented as non breaking change which would make
> this a regression.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
