You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lincoln lee (Jira)" <ji...@apache.org> on 2022/03/08 07:06:00 UTC
[jira] [Created] (FLINK-26534) shuffle by sink's primary key should cover the case that input changelog stream has a different parallelism
lincoln lee created FLINK-26534:
-----------------------------------
Summary: shuffle by sink's primary key should cover the case that input changelog stream has a different parallelism
Key: FLINK-26534
URL: https://issues.apache.org/jira/browse/FLINK-26534
Project: Flink
Issue Type: Bug
Components: Table SQL / Planner
Affects Versions: 1.15.0
Reporter: lincoln lee
FLINK-20370 fix the wrong result when sink primary key is not the same with query and introduced a new auto-keyby sink's primary key strategy for append stream if the sink's parallelism differs from input stream's.
But still exists one case to be solved:
for a changelog stream, its changelog upsert key same as sink's primary key, but sink's parallelism changed by user (via those sinks which implement the `ParallelismProvider` interface, e.g., KafkaDynamicSink), we should fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)