[jira] [Updated] (FLINK-7015) Separate OperatorConfig from StreamConfig

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-7015:
----------------------------------
      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.


> Separate OperatorConfig from StreamConfig
> -----------------------------------------
>
>                 Key: FLINK-7015
>                 URL: https://issues.apache.org/jira/browse/FLINK-7015
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Xu Pingyong
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned, pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
>  Motivation:
>             A Task contains one or more operators with chainning, however configs of operator and task are all put in StreamConfig. For example, when a opeator sets up with the StreamConfig, it can see the interface about physicalEdges or chained.task.configs that are confused.  Similarly a streamTask should not see the interface aboule chain.index.
>          So we need to separate OperatorConfig from StreamConfig. A streamTask builds execution enviroment with the streamConfig, and extract operatorConfigs from it, then build streamOperators with every operatorConfig. 
>         
>        OperatorConfig:  for the streamOperator to setup with, it constains informations that only belong to the streamOperator. It contains:
>        1)  operator information: name, id
>        2)  Serialized StreamOperator
>        3)  input serializer.
>        4)  output edges and serializers.
>        5)  chain.index
>        6) state.key.serializer
>      StreamConfig: for the streamTask to use:
>        1) in.physical.edges
>       2) out.physical.edges
>        3) chained OperatorConfigs
>        4) execution environment: checkpoint, state.backend and so on... 



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