You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "JingWei Li (Jira)" <ji...@apache.org> on 2026/04/27 06:51:00 UTC
[jira] [Commented] (FLINK-39548) CommonExecTableSourceScan uses physical row type instead of output type for upsert source key partitioning
[ https://issues.apache.org/jira/browse/FLINK-39548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076459#comment-18076459 ]
JingWei Li commented on FLINK-39548:
------------------------------------
[~libenchao] Can this ticket be assigned to me?
> CommonExecTableSourceScan uses physical row type instead of output type for upsert source key partitioning
> ------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-39548
> URL: https://issues.apache.org/jira/browse/FLINK-39548
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: JingWei Li
> Priority: Major
> Labels: pull-request-available
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> • When CommonExecTableSourceScan wraps an upsert/changelog source with configured parallelism, it derives primary-key indices from the
> physical row type.
> • If the source output is projected/reordered before the partitioning wrapper is created, those indices no longer match the actual output
> schema.
> • This causes the generated source partitioning key selector to use wrong fields.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)