You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/20 10:07:58 UTC
[jira] [Commented] (EAGLE-648) Stream router does not work properly
sometimes
[ https://issues.apache.org/jira/browse/EAGLE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591410#comment-15591410 ]
ASF GitHub Bot commented on EAGLE-648:
--------------------------------------
GitHub user garrettlish opened a pull request:
https://github.com/apache/incubator-eagle/pull/541
EAGLE-648: Stream router does not work properly sometimes
Stream router does not work properly when multiple policies use the same input stream with the same partition definition. It is because stream router bolt output maintains a map of the route specs, but the key of the map is streamId + partition information. The monitor stream may override each other if the streamId and partition are the same.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/garrettlish/incubator-eagle master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/541.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 #541
----
commit 21488410c091cd356a5e13f7b53c3ba2e51bcae1
Author: Xiancheng Li <xi...@ebay.com>
Date: 2016-10-20T10:06:38Z
EAGLE-648: Stream router does not work properly sometimes
----
> Stream router does not work properly sometimes
> ----------------------------------------------
>
> Key: EAGLE-648
> URL: https://issues.apache.org/jira/browse/EAGLE-648
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Garrett Li
> Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Stream router does not work properly when multiple policies use the same input stream with the same partition definition. It is because stream router bolt output maintains a map of the route specs, but the key of the map is streamId + partition information. The monitor stream may override each other if the streamId and partition are the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)