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

ASF GitHub Bot commented on SAMZA-1838:
---------------------------------------

GitHub user ahmedahamid opened a pull request:

    https://github.com/apache/samza/pull/623

    SAMZA-1838: Make some minor improvements to ExecutionPlanner

    

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

    $ git pull https://github.com/ahmedahamid/samza 
dev/ahabdulh/execution-planner-stylistic-improv

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

    https://github.com/apache/samza/pull/623.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 #623
    
----
commit 58e587a469c73504cd447125309b819e0fa6dce6
Author: Ahmed Abdul Hamid <ahabdulh@...>
Date:   2018-09-05T02:02:11Z

    SAMZA-1838: Make some minor improvements to ExecutionPlanner

----


> Make some minor improvements to ExecutionPlanner
> ------------------------------------------------
>
>                 Key: SAMZA-1838
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1838
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Ahmed Abdul Hamid
>            Assignee: Ahmed Abdul Hamid
>            Priority: Major
>
> * Fix case where ExecutionPlanner did not throw in response to joining 2 
> input streams with different partition counts
>  * Improve some method names in ExecutionPlanner
>  * Improve some method/field names in JobGraph
>  * Make minor improvements to createJobGraph()
>  * Rewrite updateExistingPartitions() to make it a little easier to follow
>  * Use more constrained OperatorSpec types in the associations defined in 
> calculateJoinInputPartitions()
>  * Have calculateIntStreamPartitions() throw in response to bad config for 
> job.intermediate.stream.partitions
>  * Improve some error messages



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to