[
https://issues.apache.org/jira/browse/SAMZA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197707#comment-16197707
]
ASF GitHub Bot commented on SAMZA-1292:
---------------------------------------
GitHub user prateekm opened a pull request:
https://github.com/apache/samza/pull/320
SAMZA-1292: Merge operator can be no-op when there are no streams to merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prateekm/samza small-fixes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/320.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 #320
----
commit 27efcc5f51d0b44fd4e588645cf06c45bbe825cd
Author: Prateek Maheshwari <[email protected]>
Date: 2017-10-09T20:51:47Z
SAMZA-1292: Merge operator can be no-op when there are no streams to merge
----
> Merge operator can be no-op when no streams to merge
> ----------------------------------------------------
>
> Key: SAMZA-1292
> URL: https://issues.apache.org/jira/browse/SAMZA-1292
> Project: Samza
> Issue Type: Bug
> Reporter: Prateek Maheshwari
> Assignee: Prateek Maheshwari
> Priority: Minor
> Fix For: 0.14.0
>
>
> Currently MessageStream#merge(Collection) creates a merge operator even when
> the collection of streams to merge with is empty. Can just return current
> MessageStream in this case as an optimization.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
