You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Gustavo de Morais (Jira)" <ji...@apache.org> on 2026/08/04 08:59:00 UTC

[jira] [Created] (FLINK-40324) Append-only should stay unmaterialized without an ON CONFLICT clause

Gustavo de Morais created FLINK-40324:
-----------------------------------------

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


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)