edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-156) support concurrent analytics / barrier
Date Tue, 26 Apr 2016 18:01:13 GMT

    [ https://issues.apache.org/jira/browse/QUARKS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258566#comment-15258566

ASF GitHub Bot commented on QUARKS-156:

GitHub user dlaboss opened a pull request:


    [WIP] [FEEDBACK] proposed API for "concurrent analytics"

    See https://issues.apache.org/jira/browse/QUARKS-156
    Looking for comments for the API (not the impl yet).
    This proposed high level concurrentMap() is to "make the simple simple".  I suspect some
lower level assets, that could also be directly used by apps, may be created to realize its
implementation (more on that to come).
    - happy with the semantics and signature?
    - name OK?
    - should it be ``TStream.concurrentMap()`` instead?

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dlaboss/incubator-quarks quarks-156-concurrentAnalytics

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #99
commit 3912f3f79e78b64301046ffe1b2df532de86d968
Author: Dale LaBossiere <dlaboss@us.ibm.com>
Date:   2016-04-26T17:50:27Z

    proposed API for comment


> 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
> ```
> 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

View raw message