You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2026/08/03 11:05:00 UTC
[jira] [Resolved] (FLINK-40285) MLPredictSemanticTests fails because of ON CONFLICT
[ https://issues.apache.org/jira/browse/FLINK-40285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Nuyanzin resolved FLINK-40285.
-------------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
> MLPredictSemanticTests fails because of ON CONFLICT
> ---------------------------------------------------
>
> Key: FLINK-40285
> URL: https://issues.apache.org/jira/browse/FLINK-40285
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Sergey Nuyanzin
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> {noformat}
> [ERROR] MLPredictSemanticTests>CommonSemanticTestBase.runSteps:101->CommonSemanticTestBase.runStep:178 » Validation The query has an upsert key that differs from the primary key of the sink table 'default_catalog.default_database.sink'. Primary key: [id], upsert key: none. This can lead to non-deterministic results when multiple records with different upsert keys map to the same primary key. Please specify an ON CONFLICT clause to define how conflicts should be handled: ON CONFLICT DO DEDUPLICATE (update to the latest record, state intensive, since we need to keep the entire history), or ON CONFLICT DO ERROR (fail on conflict), or ON CONFLICT DO NOTHING (keep first record).
> [ERROR] MLPredictSemanticTests>CommonSemanticTestBase.runSteps:101->CommonSemanticTestBase.runStep:178 » Validation The query has an upsert key that differs from the primary key of the sink table 'default_catalog.default_database.sink'. Primary key: [id], upsert key: none. This can lead to non-deterministic results when multiple records with different upsert keys map to the same primary key. Please specify an ON CONFLICT clause to define how conflicts should be handled: ON CONFLICT DO DEDUPLICATE (update to the latest record, state intensive, since we need to keep the entire history), or ON CONFLICT DO ERROR (fail on conflict), or ON CONFLICT DO NOTHING (keep first record).
> [ERROR] MLPredictSemanticTests>CommonSemanticTestBase.runSteps:101->CommonSemanticTestBase.runStep:178 » Validation The query has an upsert key that differs from the primary key of the sink table 'default_catalog.default_database.sink'. Primary key: [id], upsert key: none. This can lead to non-deterministic results when multiple records with different upsert keys map to the same primary key. Please specify an ON CONFLICT clause to define how conflicts should be handled: ON CONFLICT DO DEDUPLICATE (update to the latest record, state intensive, since we need to keep the entire history), or ON CONFLICT DO ERROR (fail on conflict), or ON CONFLICT DO NOTHING (keep first record).
> [ERROR] MLPredictSemanticTests>CommonSemanticTestBase.runSteps:101->CommonSemanticTestBase.runStep:178 » Validation The query has an upsert key that differs from the primary key of the sink table 'default_catalog.default_database.sink'. Primary key: [id], upsert key: none. This can lead to non-deterministic results when multiple records with different upsert keys map to the same primary key. Please specify an ON CONFLICT clause to define how conflicts should be handled: ON CONFLICT DO DEDUPLICATE (update to the latest record, state intensive, since we need to keep the entire history), or ON CONFLICT DO ERROR (fail on conflict), or ON CONFLICT DO NOTHING (keep first record).
> [ERROR] MLPredictSemanticTests>CommonSemanticTestBase.runSteps:101->CommonSemanticTestBase.runStep:178 » Validation The query has an upsert key that differs from the primary key of the sink table 'default_catalog.default_database.sink'. Primary key: [id], upsert key: none. This can lead to non-deterministic results when multiple records with different upsert keys map to the same primary key. Please specify an ON CONFLICT clause to define how conflicts should be handled: ON CONFLICT DO DEDUPLICATE (update to the latest record, state intensive, since we need to keep the entire history), or ON CONFLICT DO ERROR (fail on conflict), or ON CONFLICT DO NOTHING (keep first record).
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)