[ https://issues.apache.org/jira/browse/GEARPUMP-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531760#comment-15531760 ]
Kam Kasravi commented on GEARPUMP-206: -------------------------------------- It depends on the type of GraphStage in akka-streams. Upstreams could halt along batch boundaries. Downstreams could cache. Here are some GraphStage examples: Concat[T] * Takes multiple streams and outputs one stream formed from the input streams * by first emitting all of the elements from the first stream and then emitting * all of the elements from the second stream, etc. Interleave[T] * Interleave represents deterministic merge which takes N elements per input stream, * in-order of inputs, emits them downstream and then cycles/"wraps-around" the inputs. MergeSorted[T: Ordering] * Merge two pre-sorted streams such that the resulting stream is sorted. > 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)