[
https://issues.apache.org/jira/browse/FLINK-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085393#comment-16085393
]
ASF GitHub Bot commented on FLINK-7015:
---------------------------------------
Github user XuPingyong commented on the issue:
https://github.com/apache/flink/pull/4241
Thanks @aljoscha and @StephanEwen, I have updated this PR according to your
advice.
- Rename StreamConfig to StreamTaskConfig.
- Introduce serialisable OperatorConfig and move only those fields that are
tied to one operator within the chain from StreamTaskConfig to OperatorConfig.
Initialize the operator with an OperatorConfig.
- Introduce OperatorContext which is an interface that is a view on some
things of OperatorConfig. It is provided for setting up an operator.
> Separate OperatorConfig from StreamConfig
> -----------------------------------------
>
> Key: FLINK-7015
> URL: https://issues.apache.org/jira/browse/FLINK-7015
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Reporter: Xu Pingyong
> Assignee: Xu Pingyong
>
> 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
(v6.4.14#64029)
