[jira] [Updated] (FLINK-30129) Push projection through ChangelogNormalize
[
https://issues.apache.org/jira/browse/FLINK-30129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-30129:
---
Labels: pull-request-available (was: )
> Push projection through ChangelogNormalize
> --
>
> Key: FLINK-30129
> URL: https://issues.apache.org/jira/browse/FLINK-30129
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
>Reporter: Jark Wu
>Assignee: Jark Wu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> Currently, the ChangelogNormalize node is generated during the physical
> optimization phase. That means the projection is not pushed through
> ChangelogNormalize if the {{TableSource}} doesn't support
> {{SupportsProjectionPushDown}}. We can implement such optimization to reduce
> the state size (fewer columns in state value) and better throughput (only
> changes on the selected columns will be emitted).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-30129) Push projection through ChangelogNormalize
[
https://issues.apache.org/jira/browse/FLINK-30129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu updated FLINK-30129:
Fix Version/s: 1.18.0
> Push projection through ChangelogNormalize
> --
>
> Key: FLINK-30129
> URL: https://issues.apache.org/jira/browse/FLINK-30129
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
>Reporter: Jark Wu
>Priority: Major
> Fix For: 1.18.0
>
>
> Currently, the ChangelogNormalize node is generated during the physical
> optimization phase. That means the projection is not pushed through
> ChangelogNormalize if the {{TableSource}} doesn't support
> {{SupportsProjectionPushDown}}. We can implement such optimization to reduce
> the state size (fewer columns in state value) and better throughput (only
> changes on the selected columns will be emitted).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
