[jira] [Closed] (FLINK-40309) ML_PREDICT streaming semantic tests fail upsert-key validation

["Purushottam Sinha (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-40309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Purushottam Sinha closed FLINK-40309.
-------------------------------------
    Resolution: Duplicate

> ML_PREDICT streaming semantic tests fail upsert-key validation
> --------------------------------------------------------------
>
>                 Key: FLINK-40309
>                 URL: https://issues.apache.org/jira/browse/FLINK-40309
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner, Tests
>            Reporter: Purushottam Sinha
>            Priority: Major
>
> All 6 programs in MLPredictSemanticTests fail with ValidationException:
> "Primary key: [id], upsert key: none", demanding an explicit ON CONFLICT
> clause. The class is suffixed *Tests, so it has never executed (FLINK-40308)
> and this went unnoticed for ~6 months.
> Added 2025-11-08 by FLINK-38104; the exception landed 2026-01-30 by
> FLINK-38927 (FlinkChangelogModeInferenceProgram.scala:1228). Pre-existing,
> not a rename artifact: the original class from master fails identically 6/6.
> MLPredictRestoreTest passes only because restore tests replay a pre-compiled
> plan and skip changelog-mode inference.
> Open question: should ML_PREDICT propagate the source's primary key [id] as
> the upsert key (planner gap), or do the 6 programs need ON CONFLICT?
> Fix: decide the above, then rename to MLPredictSemanticTest so it runs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)