You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/03 15:25:12 UTC
[jira] [Commented] (QUARKS-156) support concurrent analytics /
barrier
[ https://issues.apache.org/jira/browse/QUARKS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268701#comment-15268701 ]
ASF GitHub Bot commented on QUARKS-156:
---------------------------------------
GitHub user dlaboss opened a pull request:
https://github.com/apache/incubator-quarks-website/pull/56
[QUARKS-156] [WAIT-FOR-CODE-MERGE] concurrent analytics recipe
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dlaboss/incubator-quarks-website quarks-156-concurrentAnalyticsRecipe
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quarks-website/pull/56.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 #56
----
commit 59922d4e26431ce3bfa60720edca500b6ba895c6
Author: Dale LaBossiere <dl...@us.ibm.com>
Date: 2016-05-03T13:21:22Z
[QUARKS-156] concurrent analytics recipe
----
> 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)