[
https://issues.apache.org/jira/browse/SAMZA-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704056#comment-16704056
]
ASF GitHub Bot commented on SAMZA-2013:
---------------------------------------
GitHub user ahmedahamid opened a pull request:
https://github.com/apache/samza/pull/830
SAMZA-2013: Account for cycles in graph traversal within Execution Planner
…anner
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahmedahamid/samza master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/830.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 #830
----
commit ec2eae6a96dd305f2f60d3b07c6156bbaa7e6655
Author: Ahmed Abdul Hamid <ahabdulhamid@...>
Date: 2018-11-30T00:21:22Z
SAMZA-2013: Account for cycles in graph traversal within Execution Planner
----
> Account for cycles in graph traversal within Execution Planner
> --------------------------------------------------------------
>
> Key: SAMZA-2013
> URL: https://issues.apache.org/jira/browse/SAMZA-2013
> Project: Samza
> Issue Type: Bug
> Reporter: Ahmed Abdul Hamid
> Assignee: Ahmed Abdul Hamid
> Priority: Major
>
> If a user creates a Samza high-level app where the result of a stream-join is
> sent-to the same table, {{ExecutionPlanner}} ends up infinitely traversing a
> virtual cycle between the stream-table join and send-to-table operator specs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
