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

Flink Jira Bot updated FLINK-19571:
-----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned 
pull-request-available  (was: auto-deprioritized-major auto-unassigned 
pull-request-available stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> Port Transformation translation logic to TransformationTranslator framework
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-19571
>                 URL: https://issues.apache.org/jira/browse/FLINK-19571
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>    Affects Versions: 1.12.0
>            Reporter: Kostas Kloudas
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, 
> auto-unassigned, pull-request-available
>
> Currently, the {{StreamGraphGenerator}} is responsible for:
> 1. traversing the graph of {{Transformations}}
> 2. translating them to their runtime implementations
> With the addition of the {{TransformationTranslator}} framework in 
> [FLINK-19485|https://issues.apache.org/jira/browse/FLINK-19485], we can now 
> pull the translation logic out of the {{StreamGraphGenerator}} and put it 
> into dedicated translators, one for each type of transformation.
> This umbrella issue aims at keeping track of this effort.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to