[
https://issues.apache.org/jira/browse/FLINK-26534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu closed FLINK-26534.
---------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
Fixed in master: 15d2239376244ecae6b52d0a365510ff1883a8a0
> 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
> Assignee: lincoln lee
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> 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.
> And a minor change: keyby canbe omitted when sink has single parallism
> (because none partitioner will cause worse disorder)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
