gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kam Kasravi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (GEARPUMP-206) access to upstream and downstream processors
Date Thu, 15 Sep 2016 22:10:21 GMT

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

Kam Kasravi edited comment on GEARPUMP-206 at 9/15/16 10:09 PM:
----------------------------------------------------------------

For this JIRA, GEARPUMP-193 and GEARPUMP-191 a control message to halt one or more upstreams
is I believe all we need. [~mauzhang] is there overlap with this functionality and the add
watermark - there doesn't seem to be but thought I would check. I will implement this feature
and see if it addresses current akka-streams GraphStages that require this functionality.


was (Author: kam kasravi):
For this JIRA and GEARPUMP-193 a control message to halt one or more upstreams is I believe
all we need. [~mauzhang] is there overlap with this functionality and the add watermark -
there doesn't seem to be but thought I would check. I will implement this feature and see
if it addresses current akka-streams GraphStages that require this functionality.

> access to upstream and downstream processors
> --------------------------------------------
>
>                 Key: GEARPUMP-206
>                 URL: https://issues.apache.org/jira/browse/GEARPUMP-206
>             Project: Apache Gearpump
>          Issue Type: Sub-task
>    Affects Versions: 0.8.1
>            Reporter: Kam Kasravi
>            Assignee: Kam Kasravi
>             Fix For: 0.8.2
>
>
> akka-streams requires the ability to access both upstream and downstream processors.
For upstream akka-streams will pull - we need to emulate something similar



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

Mime
View raw message