You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/01 10:54:00 UTC
[jira] [Commented] (FLINK-7015) Separate OperatorConfig from
StreamConfig
[ https://issues.apache.org/jira/browse/FLINK-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071183#comment-16071183 ]
ASF GitHub Bot commented on FLINK-7015:
---------------------------------------
GitHub user juliennju opened a pull request:
https://github.com/apache/flink/pull/4241
[FLINK-7015] [streaming] separate from OperatorConfig from StreamConfig
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Xupingyong/flink FLINK-7015
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4241.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4241
----
commit b35641760276d42e15ec17279404788760c894fc
Author: pingyong.xpy <pi...@alibaba-inc.com>
Date: 2017-07-01T10:47:00Z
[FLINK-7015] [streaming] separate from OperatorConfig from StreamConfig
----
> 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)