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

ASF GitHub Bot commented on EAGLE-7:
------------------------------------

GitHub user qingwen220 opened a pull request:

    https://github.com/apache/incubator-eagle/pull/6

    [EAGLE-7] Expose storm config as individual eagle topology config

    envContextConfig.stormConfigFile =  *absolute pathname*
    
    https://issues.apache.org/jira/browse/EAGLE-7

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-7

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-eagle/pull/6.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 #6
    
----
commit 4329ef12365fbf163fc91126271ddad0d54198b9
Author: Zhao, Qingwen <[email protected]>
Date:   2015-11-25T11:38:30Z

    change package name

commit 86e3d6d0d9684c96f5f9a145e96514eb65bc79e3
Author: Zhao, Qingwen <[email protected]>
Date:   2015-11-25T12:55:51Z

    enable storm configuration for Eagle

commit c38b9221dc7671fc87b781374fee4b44f1c32e03
Author: Zhao, Qingwen <[email protected]>
Date:   2015-11-25T12:57:31Z

    Fix quartz job have already exists error

----


> expose storm config as individual eagle topology config
> -------------------------------------------------------
>
>                 Key: EAGLE-7
>                 URL: https://issues.apache.org/jira/browse/EAGLE-7
>             Project: Eagle
>          Issue Type: Improvement
>         Environment: production linux
>            Reporter: Edward Zhang
>            Assignee: Zhao, Qingwen
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Storm has many configurations which can be configured through storm.yaml, and 
> those configurations are actually can be per topology. Eagle should have a 
> capability to expose all the configurations through Eagle configuration. Some 
> examples are 
> topology.acker.executors: 2
> topology.tasks: 8     
> topology.max.spout.pending: 1000
> topology.executor.receive.buffer.size: 16384
> topology.executor.send.buffer.size: 16384
> Today we only have parallelism of bolt/spout can be configured through eagle 
> configuration.



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

Reply via email to