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

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

GitHub user gyfora opened a pull request:

    https://github.com/apache/flink/pull/634

    [FLINK-1948] [streaming] Manual task slot sharing settings added for stream 
operators

    This PR introduces 2 new methods for the streaming operators to give 
control over the slot sharing settings for task slots.
    
    The javadocs for the 2 methods explain the behaviour.
    
    It also contains a method name refactor getVertex -> getStreamNode and some 
comments for controlling the chaining behaviour.

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

    $ git pull https://github.com/mbalassi/flink slot

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

    https://github.com/apache/flink/pull/634.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 #634
    
----
commit 4f64768e260a8768e241ec19ad14f0af81937095
Author: Gyula Fora <[email protected]>
Date:   2015-04-27T17:24:26Z

    [FLINK-1948] [streaming] Manual task slot sharing settings added for stream 
operators

----


> Add manual task slot handling for streaming jobs
> ------------------------------------------------
>
>                 Key: FLINK-1948
>                 URL: https://issues.apache.org/jira/browse/FLINK-1948
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>
> Currently, all stream operators are automatically assigned to the same task 
> sharing group, and the user has no control over this setting. We should add a 
> way to manually affect the way operators are allocated to task manager slots.



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

Reply via email to