[
https://issues.apache.org/jira/browse/FLINK-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072123#comment-16072123
]
ASF GitHub Bot commented on FLINK-7015:
---------------------------------------
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/4241
Hi @juliennju,
thanks for opening this PR and for interest in changing these parts of
these code.
However, these changes touch somewhat intricate parts of the code where
some other people are working and where also several people have plans and
thoughts about how to improve things. Before doing work on these parts I would
suggest to start a `[DISCUSS]` thread on the dev mailing list to 1) describe
your motivation for changing these parts, 2) see what other people have already
thought about this, and 3) to coordinate changes with other people working on
this.
I'm sorry for the inconvenience this causes you because you already started
working on code.
I'm aware of at least @StefanRRichter, @StephanEwen and me as having spend
some cycles thinking about changes in these parts.
For example, we would definitely need to discuss what constitutes "operator
config", "task config" and general "stream config" and how we want to shield
the different components from each other and make them more modular.
What do you think?
> 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
>
> Now stream config contains configs not only the batch task needs, but also
> the operator needs, so stream config can see configs of the operator, and
> operator can see configs of the batch task.
> We need to separate operator config from stream config, and they can only
> see configs of themselves.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
