flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2525) Add configuration support in Storm-compatibility
Date Mon, 14 Sep 2015 22:22:47 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744399#comment-14744399

ASF GitHub Bot commented on FLINK-2525:

Github user fhueske commented on the pull request:

    Actually, I think going through the `TaskConfig` as proposed by @mjsax is the cleaner
way. Going through the system-internal `JobConfiguration` and exposing it to user programs
is not a good choice, in my opinion. 
    The purpose of `TaskConfig` is exactly to give parameters to a task (function, spout).
Also the `StreamingRuntimeContext` would not need to be adapted, because it already offers
a method `getTaskStubParameters()`. Would that work as well or are there major issues preventing
you from using the `TaskConfig`?

> Add configuration support in Storm-compatibility
> ------------------------------------------------
>                 Key: FLINK-2525
>                 URL: https://issues.apache.org/jira/browse/FLINK-2525
>             Project: Flink
>          Issue Type: New Feature
>          Components: Storm Compatibility
>            Reporter: fangfengbin
>            Assignee: fangfengbin
> Spouts and Bolt are initialized by a call to `Spout.open(...)` and `Bolt.prepare()`,
respectively. Both methods have a config `Map` as first parameter. This map is currently not
populated. Thus, Spouts and Bolts cannot be configure with user defined parameters. In order
to support this feature, spout and bolt wrapper classes need to be extended to create a proper
`Map` object. Furthermore, the clients need to be extended to take a `Map`, translate it into
a Flink `Configuration` that is forwarded to the wrappers for proper initialization of the

This message was sent by Atlassian JIRA

View raw message