[ 
https://issues.apache.org/jira/browse/FLINK-37104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wenkai Qi updated FLINK-37104:
------------------------------
    Description: 
Code simplification and cleaning related to Flink CDC YAML Transform.

For example: 

Task construction stage: Each TransformRule corresponds to one PostTransformer, 
and one PostTransformer corresponds to one TransformProjection and 
TransformFilter.
Task running stage: Each TableId corresponds to one or more projection rule 
Strings. One TableId plus one projection rule String corresponds to one 
TransformProjectionProcessor, and one TransformProjectionProcessor corresponds 
to one TransformProjection.
In the two stages, the correspondence of TransformProjection is different. 
TransformRule and the projection rule String have a one-to-one relationship, so 
in the task construction stage, a TransformRule only corresponds to one 
TransformProjection; in the task running stage, the projection rule String 
corresponds to multiple TransformProjections.
TransformProjection should be split into two classes according to the usage 
scenarios.

> Code simplification and cleaning related to Flink CDC YAML Transform
> --------------------------------------------------------------------
>
>                 Key: FLINK-37104
>                 URL: https://issues.apache.org/jira/browse/FLINK-37104
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: Wenkai Qi
>            Priority: Minor
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Code simplification and cleaning related to Flink CDC YAML Transform.
> For example: 
> Task construction stage: Each TransformRule corresponds to one 
> PostTransformer, and one PostTransformer corresponds to one 
> TransformProjection and TransformFilter.
> Task running stage: Each TableId corresponds to one or more projection rule 
> Strings. One TableId plus one projection rule String corresponds to one 
> TransformProjectionProcessor, and one TransformProjectionProcessor 
> corresponds to one TransformProjection.
> In the two stages, the correspondence of TransformProjection is different. 
> TransformRule and the projection rule String have a one-to-one relationship, 
> so in the task construction stage, a TransformRule only corresponds to one 
> TransformProjection; in the task running stage, the projection rule String 
> corresponds to multiple TransformProjections.
> TransformProjection should be split into two classes according to the usage 
> scenarios.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to