[
https://issues.apache.org/jira/browse/FLINK-40285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Nuyanzin updated FLINK-40285:
------------------------------------
Description:
{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}
> 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
>
> {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)
