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

ASF GitHub Bot commented on FLINK-2525:
---------------------------------------

Github user fhueske commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1046#discussion_r39453328
  
    --- Diff: 
flink-staging/flink-streaming/flink-streaming-core/src/main/java/org/apache/flink/streaming/runtime/tasks/StreamingRuntimeContext.java
 ---
    @@ -91,7 +91,16 @@ public InputSplitProvider getInputSplitProvider() {
        public Configuration getTaskStubParameters() {
                return new 
TaskConfig(env.getTaskConfiguration()).getStubParameters();
        }
    -   
    +
    +   /**
    +    * Returns the job configuration.
    +    *
    +    * @return The job configuration.
    +    */
    +   public Configuration getJobConfiguration() {
    +           return new Configuration(env.getJobConfiguration());
    --- End diff --
    
    The `JobConfiguration` is a system-internal configuration. I am not sure 
that it is a good idea to give access to it in the `StreamingRuntimeContext`. 
This change will be visible for all DataStream programs.


> 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 map.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to