edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QUARKS-156) support concurrent analytics / barrier
Date Tue, 26 Apr 2016 15:31:12 GMT
Dale LaBossiere created QUARKS-156:
--------------------------------------

             Summary: support concurrent analytics / barrier
                 Key: QUARKS-156
                 URL: https://issues.apache.org/jira/browse/QUARKS-156
             Project: Quarks
          Issue Type: New Feature
          Components: API
            Reporter: Dale LaBossiere
            Assignee: Dale LaBossiere


Consider a pipeline of *independent* analytics, each enriching some tuple with additional
information:

```
readings<T> -> A1 -> A2 -> A3 -> results<R>
```

If the analytics are independent and non-trivial / time consuming, there's a desire to run
the analytics concurrently for each tuple with a graph logically like:

```
                           /->  A1  ->\
readings<T> ->  |->  A2   ->| -> result<R>
                           \->  A3  ->/
```

I'm using the term "concurrent" instead of "parallel".  Java8 Streams', and IBM Streams Java
API's and SPL's, use of "parallel" is for "parallel-tuple processing": multiple tuples, each
being processed in parallel in its own "channel" of the same replicated pipeline of operations.

I'm going to use a pull-request to capture API proposals/discussion.



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

Mime
View raw message