[
https://issues.apache.org/jira/browse/QUARKS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267265#comment-15267265
]
ASF GitHub Bot commented on QUARKS-165:
---------------------------------------
GitHub user dlaboss opened a pull request:
https://github.com/apache/incubator-quarks/pull/104
[QUARKS-165] [WIP] [skip-ci] add traditional parallel analytics
- Add PlumbingStreams.parallel()
- Add PlumbingStreams.parallelMap()
These are in contrast to the new concurrent[Map]() in PR-99.
The impl is dependent on functionality in PR-99 and can't be merged
until that is merged. The hack makes the tests runnable and they pass.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dlaboss/incubator-quarks
quarks-165-parallelAnalytics
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quarks/pull/104.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 #104
----
commit c4d6a8559dcadef7d523c2f96cd36994d59524be
Author: Dale LaBossiere <[email protected]>
Date: 2016-05-02T18:56:35Z
[QUARKS-165] [WIP] [skip-ci] add traditional parallel analytics
- Add PlumbingStreams.parallel()
- Add PlumbingStreams.parallelMap()
These are in contrast to the new concurrent[Map]() in PR-99.
The impl is dependent on functionality in PR-99 and can't be merged
until that is merged. The hack makes the tests runnable and they pass.
----
> support tuple-parallel analytics
> --------------------------------
>
> Key: QUARKS-165
> URL: https://issues.apache.org/jira/browse/QUARKS-165
> Project: Quarks
> Issue Type: New Feature
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
>
> Add the ability to easily create traditional parallel pipeline flows:
> N-channels of the same pipeline logic, with a splitter controlling the tuple
> distribution, and union'ing the results from the channels.
> I'm creating a PR with the API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
