[
https://issues.apache.org/jira/browse/FLINK-40285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101342#comment-18101342
]
Sergey Nuyanzin commented on FLINK-40285:
-----------------------------------------
Merged as
[12197ea92a5667073bc0c6810e526a39979d835c|https://github.com/apache/flink/commit/12197ea92a5667073bc0c6810e526a39979d835c]
> 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
>
> {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)
