You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@edgent.apache.org by wc...@apache.org on 2016/03/29 18:54:46 UTC
[3/3] incubator-quarks-website git commit: from
7d0c62c6bcd2f6982c6486b4ae1fa35f05a9a2fd
from 7d0c62c6bcd2f6982c6486b4ae1fa35f05a9a2fd
Project: http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/commit/b72be05e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/tree/b72be05e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/diff/b72be05e
Branch: refs/heads/asf-site
Commit: b72be05e78446c8ca34f386af6fa4ee6c8340302
Parents: f8a5040
Author: wcmarsha <wc...@us.ibm.com>
Authored: Tue Mar 29 09:54:14 2016 -0700
Committer: wcmarsha <wc...@us.ibm.com>
Committed: Tue Mar 29 09:54:14 2016 -0700
----------------------------------------------------------------------
content/404.html | 45 +-
content/algolia_search.json | 30 +-
content/docs/committers.html | 45 +-
content/docs/common-quarks-operations.html | 49 +-
content/docs/community.html | 73 +-
content/docs/console.html | 45 +-
content/docs/faq.html | 45 +-
content/docs/getinvolved.html | 578 -------------
content/docs/home.html | 45 +-
content/docs/overview.html | 45 +-
content/docs/quarks-getting-started.html | 45 +-
content/docs/quarks_index.html | 45 +-
content/docs/quickstart.html | 45 +-
content/docs/samples.html | 45 +-
content/docs/search.html | 45 +-
content/docs/tag_collaboration.html | 49 +-
content/docs/tag_content_types.html | 49 +-
content/docs/tag_formatting.html | 49 +-
content/docs/tag_getting_started.html | 49 +-
content/docs/tag_mobile.html | 49 +-
content/docs/tag_navigation.html | 49 +-
content/docs/tag_publishing.html | 49 +-
content/docs/tag_single_sourcing.html | 49 +-
content/docs/tag_special_layouts.html | 49 +-
content/prince-file-list.txt | 7 +-
...treams_processing_results_topology_graph.jpg | Bin 0 -> 171599 bytes
...pe_combining_streams_processing_results.html | 823 +++++++++++++++++++
...ipe_different_processing_against_stream.html | 45 +-
content/recipes/recipe_hello_quarks.html | 45 +-
content/recipes/recipe_source_function.html | 45 +-
content/recipes/recipe_value_out_of_range.html | 45 +-
content/search.json | 22 +-
content/title-checker.html | 77 ++
content/titlepage.html | 47 +-
content/tocpage.html | 53 +-
content/urls_mydoc.txt | 13 +-
36 files changed, 2055 insertions(+), 833 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/404.html
----------------------------------------------------------------------
diff --git a/content/404.html b/content/404.html
index ef28520..5710029 100644
--- a/content/404.html
+++ b/content/404.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -534,14 +543,36 @@ $('#toc').on('click', 'a', function() {
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/algolia_search.json
----------------------------------------------------------------------
diff --git a/content/algolia_search.json b/content/algolia_search.json
index 713af33..5533604 100644
--- a/content/algolia_search.json
+++ b/content/algolia_search.json
@@ -26,7 +26,7 @@
"keywords": "",
"url": "../docs/common-quarks-operations",
"summary": "",
-"body": "# Common Quarks OperationsIn the first [getting started guide](quarks-getting-started), we covered a \"hello world\" Quarks application where we read from a device's simulated temperature sensor. Yet Quarks supports more operations than simple filtering. Data analysis and streaming require a suite of functionality, the most important components of which will be outlined below.## TStream.map()TStream.map() is arguably the most used method in the Quarks API. Its two main purposes are to perform stateful or stateless operations on a stream's tuples, and to produce a TStream with tuples of a different type from that of the calling stream.#### Changing a TStream's Tuple TypeIn addition to filtering tuples, TStreams support operations that *transform* tuples from one Java type to another by invoking the TStream.map() method.This is useful in cases such as calculating the floating point average of a list of Integers, or tokenizing a Java String into a list of Strings. To demonstra
te this, let's say we have a TStream which contains a few lines, each of which contains multiple words:```java TStream lines = topology.strings( \"this is a line\", \"this is another line\", \"there are three lines now\", \"and now four\" );```We then want to print the third word in each line. The best way to do this is to convert each line to a list of Strings by tokenizing them. We can do this in one line of code with the TStream.map() method:```java TStream > wordsInLine = lines.map(tuple -> Arrays.asList(tuple.split(\" \")));```Since each tuple is now a list of strings, the *wordsInLine* stream is of type List. As you can see, the map() method has the ability to change the type of the TStream. Finally, we can use the *wordsInLine* stream to print the third word in each line.```java wordsInLine.sink(list -> System.out.println(list.get(2)));```As mentioned in the [getting started guide](quarks-getting-started), a TStream
can be parameterized to any serializable Java type, including ones created by the user.#### Performing Stateful OperationsIn all previous examples, the operations performed on a TStream have been stateless; keeping track of information over multiple invocations of the same operation has not been necessary. What if we want to keep track of the number of Strings sent over a stream? To do this, we need our TStream.map() method to contain a counter as state.This can be achieved by creating an anonymous Function class, and giving it the required fields.```java TStream streamOfStrings = ...; TStream counts = streamOfStrings.map(new Function(){ int count = 0; @Override public Integer apply(String arg0) { count = count + 1; return count; } });```The *count* field will now contain the number of Strings which were sent over streamOfStrings. Although this is a simple example, the anonymous Function passed to
TStream.map() can contain any kind of state! This could be a HashMap, a running list of tuples, or any serializable Java type. The state will be maintained throughout the entire runtime of your application."
+"body": "# Common Quarks OperationsIn the first [getting started guide](quarks-getting-started), we covered a \"hello world\" Quarks application where we read from a device's simulated temperature sensor. Yet Quarks supports more operations than simple filtering. Data analysis and streaming require a suite of functionality, the most important components of which will be outlined below.## TStream.map()TStream.map() is arguably the most used method in the Quarks API. Its two main purposes are to perform stateful or stateless operations on a stream's tuples, and to produce a TStream with tuples of a different type from that of the calling stream.### Changing a TStream's Tuple TypeIn addition to filtering tuples, TStreams support operations that *transform* tuples from one Java type to another by invoking the TStream.map() method.This is useful in cases such as calculating the floating point average of a list of Integers, or tokenizing a Java String into a list of Strings. To demonstrat
e this, let's say we have a TStream which contains a few lines, each of which contains multiple words:```java TStream lines = topology.strings( \"this is a line\", \"this is another line\", \"there are three lines now\", \"and now four\" );```We then want to print the third word in each line. The best way to do this is to convert each line to a list of Strings by tokenizing them. We can do this in one line of code with the TStream.map() method:```java TStream > wordsInLine = lines.map(tuple -> Arrays.asList(tuple.split(\" \")));```Since each tuple is now a list of strings, the *wordsInLine* stream is of type List. As you can see, the map() method has the ability to change the type of the TStream. Finally, we can use the *wordsInLine* stream to print the third word in each line.```java wordsInLine.sink(list -> System.out.println(list.get(2)));```As mentioned in the [getting started guide](quarks-getting-started), a TStream c
an be parameterized to any serializable Java type, including ones created by the user.### Performing Stateful OperationsIn all previous examples, the operations performed on a TStream have been stateless; keeping track of information over multiple invocations of the same operation has not been necessary. What if we want to keep track of the number of Strings sent over a stream? To do this, we need our TStream.map() method to contain a counter as state.This can be achieved by creating an anonymous Function class, and giving it the required fields.```java TStream streamOfStrings = ...; TStream counts = streamOfStrings.map(new Function(){ int count = 0; @Override public Integer apply(String arg0) { count = count + 1; return count; } });```The *count* field will now contain the number of Strings which were sent over streamOfStrings. Although this is a simple example, the anonymous Function passed to T
Stream.map() can contain any kind of state! This could be a HashMap, a running list of tuples, or any serializable Java type. The state will be maintained throughout the entire runtime of your application."
},
@@ -39,7 +39,7 @@
"keywords": "",
"url": "../docs/community",
"summary": "",
-"body": "Every volunteer project obtains its strength from the people involved in it. We invite you to participate as much or as little as you choose.You can:* Use our project and provide a feedback.* Provide us with the use-cases.* Report bugs and submit patches.* Contribute code, javadocs, documentation.Visit the [Contributing](http://www.apache.org/foundation/getinvolved.html) page and read [DEVELOPMENT.md] (https://github.com/apache/incubator-quarks/blob/master/DEVELOPMENT.md) at the top of the code tree for more information.### Mailing listGet help using {{ site.data.project.short_name }} or contribute to the project on our mailing lists:{% if site.data.project.user_list %}* [site.data.project.user_list](mailto:{{ site.data.project.user_list }}) is for usage questions, help, and announcements. [subscribe](mailto:{{ site.data.project.user_list_subscribe }}?subject=send this email to subscribe), [unsubscribe](mailto:{{ site.data.project.dev_list_unsubscribe }}?subject=send th
is email to unsubscribe), [archives]({{ site.data.project.user_list_archive_mailarchive }}){% endif %}* [{{ site.data.project.dev_list }}](mailto:{{ site.data.project.dev_list }}) is for people who want to contribute code to {{ site.data.project.short_name }}. [subscribe](mailto:{{ site.data.project.dev_list_subscribe }}?subject=send this email to subscribe), [unsubscribe](mailto:{{ site.data.project.dev_list_unsubscribe }}?subject=send this email to unsubscribe), [archives]({{ site.data.project.dev_list_archive_mailarchive }})* [{{ site.data.project.commits_list }}](mailto:{{ site.data.project.commits_list }}) is for commit messages and patches to {{ site.data.project.short_name }}. [subscribe](mailto:{{ site.data.project.commits_list_subscribe }}?subject=send this email to subscribe), [unsubscribe](mailto:{{ site.data.project.commits_list_unsubscribe }}?subject=send this email to unsubscribe), [archives]({{ site.data.project.commits_list_archive_mailarchive }})### Issue trackerWe
use Jira here: [https://issues.apache.org/jira/browse/QUARKS](https://issues.apache.org/jira/browse/QUARKS)#### Bug ReportsFound bug? Enter an issue in the [Issue Tracker](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}).Before submitting an issue, please:* Verify that the bug does in fact exist.* Search the issue tracker to verify there is no existing issue reporting the bug you've found.* Consider tracking down the bug yourself in the {{ site.data.project.short_name }} source and submitting apull request along with your bug report. This is a great time saver for the {{ site.data.project.short_name }} developers and helps ensure the bug will be fixed quickly.#### Feature RequestsEnhancement requests for new features are also welcome. The more concrete and rationale the request is, the greater the chance it will incorporated into future releases. [https://issues.apache.org/jira/browse/{{ site.data.project.jira }}](https://issues.apache.org/jira/browse/{{ site.d
ata.project.jira }})### Source CodeThe project sources are accessible via the [source code repository]({{ site.data.project.source_repository }}) which is also mirrored in [GitHub]({{ site.data.project.source_repository_mirror }})### Website Source CodeThe project website sources are accessible via the [website source code repository]({{ site.data.project.website_repository }}) which is also mirrored in [GitHub]({{ site.data.project.website_repository_mirror }})"
+"body": "Every volunteer project obtains its strength from the people involved in it. We invite you to participate as much or as little as you choose.You can:* Use our project and provide a feedback.* Provide us with the use-cases.* Report bugs and submit patches.* Contribute code, javadocs, documentation.Visit the [Contributing](http://www.apache.org/foundation/getinvolved.html) page for general Apache contribution information. If you plan to make any significant contribution, you will need to have an Individual Contributor License Agreement [\\(ICLA\\)] (https://www.apache.org/licenses/icla.txt) on file with Apache.### Mailing listGet help using {{ site.data.project.short_name }} or contribute to the project on our mailing lists:{% if site.data.project.user_list %}* [site.data.project.user_list](mailto:{{ site.data.project.user_list }}) is for usage questions, help, and announcements. [subscribe](mailto:{{ site.data.project.user_list_subscribe }}?subject=send this email to subscr
ibe), [unsubscribe](mailto:{{ site.data.project.dev_list_unsubscribe }}?subject=send this email to unsubscribe), [archives]({{ site.data.project.user_list_archive_mailarchive }}){% endif %}* [{{ site.data.project.dev_list }}](mailto:{{ site.data.project.dev_list }}) is for people who want to contribute code to {{ site.data.project.short_name }}. [subscribe](mailto:{{ site.data.project.dev_list_subscribe }}?subject=send this email to subscribe), [unsubscribe](mailto:{{ site.data.project.dev_list_unsubscribe }}?subject=send this email to unsubscribe), [archives]({{ site.data.project.dev_list_archive_mailarchive }})* [{{ site.data.project.commits_list }}](mailto:{{ site.data.project.commits_list }}) is for commit messages and patches to {{ site.data.project.short_name }}. [subscribe](mailto:{{ site.data.project.commits_list_subscribe }}?subject=send this email to subscribe), [unsubscribe](mailto:{{ site.data.project.commits_list_unsubscribe }}?subject=send this email to unsubscribe
), [archives]({{ site.data.project.commits_list_archive_mailarchive }})### Issue trackerWe use Jira here: [https://issues.apache.org/jira/browse/{{ site.data.project.jira }}](https://issues.apache.org/jira/browse/{{ site.data.project.jira }})#### Bug ReportsFound bug? Enter an issue in [Jira](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}).Before submitting an issue, please:* Verify that the bug does in fact exist.* Search the issue tracker to verify there is no existing issue reporting the bug you've found.* Consider tracking down the bug yourself in the {{ site.data.project.short_name }} source and submitting a pull request along with your bug report. This is a great time saver for the {{ site.data.project.short_name }} developers and helps ensure the bug will be fixed quickly.#### Feature RequestsEnhancement requests for new features are also welcome. The more concrete the request is and the better rationale you provide, the greater the chance it will incor
porated into future releases. [https://issues.apache.org/jira/browse/{{ site.data.project.jira }}](https://issues.apache.org/jira/browse/{{ site.data.project.jira }})### Source CodeThe project sources are accessible via the [source code repository]({{ site.data.project.source_repository }}) which is also mirrored in [GitHub]({{ site.data.project.source_repository_mirror }}). When you are considering a code contribution, make sure there is an [Issue](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}) that describes your work or the bug you are fixing. For significant contributions, please discuss your proposed changes in the Issue so that others can comment on your plans. Someone else may be working on the same functionality, so it's good to communicate early and often. A committer is more likely to accept your change if there is clear information in the Issue. To contribute, [fork](https://help.github.com/articles/fork-a-repo/) the [mirror]({{ site.data.project.
source_repository_mirror }}) and issue a pull request. Put the Jira issue number, e.g. {{ site.data.project.jira }}-100 in the pull request title. The tag [WIP] can also be used in the title of pull requests to indicate that you are not ready to merge but want feedback. Remove [WIP] when you are ready for merge. Make sure you document your code and contribute tests along with the code.Read [DEVELOPMENT.md] (https://github.com/apache/incubator-quarks/blob/master/DEVELOPMENT.md) at the top of the code tree for details on setting up your development environment. ### Web Site and Documentation Source CodeThe project website and documentation sources are accessible via the [website source code repository]({{ site.data.project.website_repository }}) which is also mirrored in [GitHub]({{ site.data.project.website_repository_mirror }}). Contributing changes to the web site and documentation is similar to contributing code. Follow the instructions in the Source Code section above, but fork
and issue a pull request against the [web site mirror]({{ site.data.project.website_repository_mirror }}). Follow the instructions in the top level [README.md] ({{ site.data.project.website_repository_mirror }}/blob/master/README.md) for details on contributing to the web site and documentation. You will need to use Markdown and Jekyll to develop pages. See:* [Markdown Cheat Sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)* [Jekyll on linux and Mac] (https://jekyllrb.com/) * [Jekyll on Windows] (https://jekyllrb.com/docs/windows/) is not officially supported but people have gotten it to work."
},
@@ -73,19 +73,6 @@
{
-"title": "Get Involved",
-"tags": "",
-"keywords": "",
-"url": "../docs/getinvolved",
-"summary": "",
-"body": "# Get Involved with QuarksWelcome to the Quarks community! We would love to have you participate as a user of Quarks, a contributor or both.## Contribute CodeIf you plan to make any significant contribution, you will need to have a Contributor License Agreement [(CLA)](https://github.com/quarks-edge/quarks/blob/master/licences/Quarks-cla-individual.pdf) on file. Get a copy of the CLA, fill it out and follow the instructions in the CLA to file it. Committers will require a CLA before they commit contributions.When you are considering a code contribution, make sure there is an [Issue](https://github.com/quarks-edge/quarks/issues) that describes your work or the bug you are fixing. For significant contributions, please discuss your proposed changes in the Issue so that others can comment on your plans. Someone else may be working on the same functionality, so it's good to communicate early and often. A committer is more likely to accept your change if there is clear info
rmation in the Issue. The best way to start on the code is to [fork](https://help.github.com/articles/fork-a-repo/) Quarks and make changes in your fork. When you're happy with the changes in your fork, issue a [pull request](https://github.com/quarks-edge/quarks/pulls). Make sure you document your code and contribute tests along with the code.We welcome new committers. Get information on committers [here](committers).## Contribute Documentation for the Web SiteContributing documentation is similar to contributing code. Follow the instructions in the Contribute Code Section above. If you are submitting documentation for the web site, you will need to use Markdown and Jekyll to develop your web pages.* [Markdown Cheat Sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)* [Using Jekyll with Pages](https://help.github.com/articles/using-jekyll-with-pages/)## Use Quarks and Participate in the CommunityPlease [download](https://github.com/quarks-edge/quarks/rele
ases/latest) the latest release of Quarks and use it. We would love to get your feedback. Create an [Issue](https://github.com/quarks-edge/quarks/issues) for any bugs you encounter, requests for enhancements or questions you may have. Feel free to comment on existing issues as well. You are welcome to update the [wiki](https://github.com/quarks-edge/quarks/wiki) with any information you want to provide to help others. Just link in any new pages, to be sure they are not lost. If you have any significant comments on existing wiki pages, open an Issue to have a discussion."
-
-},
-
-
-
-
-{
"title": "Introduction",
"tags": "getting_started",
"keywords": "",
@@ -167,6 +154,19 @@
{
+"title": "Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream",
+"tags": "",
+"keywords": "",
+"url": "../recipes/recipe_combining_streams_processing_results",
+"summary": "",
+"body": "In some cases, a developer might want to perform analytics taking into account the nature of the data. Say, for example, the data consists of log records each containing a level attribute. It would be logical to handle *fatal* log messages differently than *info* or *debug* messages. The same reasoning could also apply in the healthcare industry.Suppose doctors at a hospital would like to monitor patients' states using a bedside heart monitor. They would like to apply different analytics to the monitor readings based on the severity category of the blood pressure readings. For instance, if a patient is in hypertensive crisis (due to extremely high blood pressure), the doctors may want to analyze the patient's heart rate to determine risk of a stroke.In this instance, we can use `split` to separate blood pressure readings by category (five in total) and perform additional analytics on each of the resulting streams. After processing the data, we show how to define a new strea
m of alerts for each category and `union` the streams to create a stream containing all alerts.## Setting up the applicationWe assume that the environment has been set up following the steps outlined in the [Getting Started Guide](../docs/quarks-getting-started).First, we need to define a class for a heart monitor. We generate random blood pressure readings, each consisting of the systolic pressure (the top number) and the diastolic pressure (the bottom number). For example, with a blood pressure of 115/75 (read as \"115 over 75\"), the systolic pressure is 115 and the diastolic pressure is 75. These two pressures are stored in a `map`, and each call to `get()` returns new values.```java import java.util.HashMap; import java.util.Map; import java.util.Random; import quarks.function.Supplier; public class HeartMonitorSensor implements Supplier> { private static final long serialVersionUID = 1L; // Initial blood pressure public Integer currentSystol
ic = 115; public Integer currentDiastolic = 75; Random rand; public HeartMonitorSensor() { rand = new Random(); } /** * Every call to this method returns a map containing a random systolic * pressure and a random diastolic pressure. */ @Override public Map get() { // Change the current pressure by some random amount between -2 and 2 Integer newSystolic = rand.nextInt(2 + 1 + 2) - 2 + currentSystolic; currentSystolic = newSystolic; Integer newDiastolic = rand.nextInt(2 + 1 + 2) - 2 + currentDiastolic; currentDiastolic = newDiastolic; Map pressures = new HashMap(); pressures.put(\"Systolic\", currentSystolic); pressures.put(\"Diastolic\", currentDiastolic); return pressures; } }```Now, let's start our application by creating a `DirectProvider` and `Topology`. We choose a `DevelopmentProvider` so
that we can view the topology graph using the console URL. We have also created a `HeartMonitor`.```java import java.util.HashSet; import java.util.List; import java.util.Map; import java.util.Set; import java.util.concurrent.TimeUnit; import quarks.console.server.HttpServer; import quarks.function.ToIntFunction; import quarks.providers.development.DevelopmentProvider; import quarks.providers.direct.DirectProvider; import quarks.samples.utils.sensor.HeartMonitorSensor; import quarks.topology.TStream; import quarks.topology.Topology; public class CombiningStreamsProcessingResults { public static void main(String[] args) { HeartMonitorSensor monitor = new HeartMonitorSensor(); DirectProvider dp = new DevelopmentProvider(); System.out.println(dp.getServices().getService(HttpServer.class).getConsoleUrl()); Topology top = dp.newTopology(\"heartMonitor\"); // The rest of the code pieces b
elong here } }```## Generating heart monitor sensor readingsThe next step is to simulate a stream of readings. In our `main()`, we use the `poll()` method to generate a flow of tuples (readings), where each tuple arrives every millisecond. Unlikely readings are filtered out.```java // Generate a stream of heart monitor readings TStream> readings = top .poll(monitor, 1, TimeUnit.MILLISECONDS) .filter(tuple -> tuple.get(\"Systolic\") > 50 && tuple.get(\"Diastolic\") > 30) .filter(tuple -> tuple.get(\"Systolic\") > split(int n, ToIntFunction splitter)````split` returns a `List` of `TStream` objects, where each item in the list is one of the resulting output streams. In this case, one stream in the list will contain a flow of tuples where the blood pressure reading belongs to one of the five blood pressure categories. Another stream will contain a flow of tuples where the blood pressure reading belongs to a different blood pressure catego
ry, and so on.There are two input parameters. You must specify `n`, the number of output streams, as well as a `splitter` method. `splitter` processes each incoming tuple individually and determines on which of the output streams the tuple will be placed. In this method, you can break down your placement rules into different branches, where each branch returns an integer indicating the index of the output stream in the list.Going back to our example, let's see how we can use `split` to achieve our goal. We pass in `6` as the first argument, as we want five output streams (i.e., a stream for each of the five different blood pressure categories) in addition one stream for invalid values. Our `splitter` method should then define how tuples will be placed on each of the five streams. We define a rule for each category, such that if the systolic and diastolic pressures of a reading fall in a certain range, then that reading belongs to a specific category. For example, if we are processin
g a tuple with a blood pressure reading of 150/95 (*High Blood Pressure (Hypertension) Stage 1* category), then we return `2`, meaning that the tuple will be placed in the stream at index `2` in the `categories` list. We follow a similar process for the other 4 categories, ordering the streams from lowest to highest severity.```java List>> categories = readings.split(6, tuple -> { int s = tuple.get(\"Systolic\"); int d = tuple.get(\"Diastolic\"); if (s = 120 && s = 80 && d = 140 && s = 90 && d = 160 && s = 100 && d = 180 && d >= 110) { // Hypertensive Crisis return 4; } else { // Invalid return -1; } });```Note that instead of `split`, we could have performed five different `filter` operations. However, `split` is favored for cleaner code and more efficient processing as each tuple is only analyzed once.## Applying different processing against the streams to generate alertsAt this point, we have 6
output streams, one for each blood pressure category and one for invalid values (which we will ignore). We can easily retrieve a stream by using the standard `List` operation `get()`. For instance, we can retrieve all heart monitor readings with a blood pressure reading in the *Normal* category by retrieving the `TStream` at index `0` as we defined previously. Similarly, we can retrieve the other streams associated with the other four categories. The streams are tagged so that we can easily locate them in the topology graph.```java // Get each individual stream TStream> normal = categories.get(0).tag(\"normal\"); TStream> prehypertension = categories.get(1).tag(\"prehypertension\"); TStream> hypertension_stage1 = categories.get(2).tag(\"hypertension_stage1\"); TStream> hypertension_stage2 = categories.get(3).tag(\"hypertension_stage2\"); TStream> hypertensive = categories.get(4).tag(\"hypertensive\");```The hospital can then use these streams to perform analytics o
n each stream and generate alerts based on the blood pressure category. For this simple example, a different number of transformations/filters is applied to each stream (known as a processing pipeline) to illustrate that very different processing can be achieved that is specific to the category at hand.```java // Category: Normal TStream normalAlerts = normal .filter(tuple -> tuple.get(\"Systolic\") > 80 && tuple.get(\"Diastolic\") > 50) .tag(\"normal\") .map(tuple -> { return \"All is normal. BP is \" + tuple.get(\"Systolic\") + \"/\" + tuple.get(\"Diastolic\") + \".\\n\"; }) .tag(\"normal\"); // Category: Prehypertension category TStream prehypertensionAlerts = prehypertension .map(tuple -> { return \"At high risk for developing hypertension. BP is \" + tuple.get(\"Systolic\") + \"/\" + tuple.get(\"Diastolic\") + \".\\n\"; }) .ta
g(\"prehypertension\"); // Category: High Blood Pressure (Hypertension) Stage 1 TStream hypertension_stage1Alerts = hypertension_stage1 .map(tuple -> { return \"Monitor closely, patient has high blood pressure. \" + \"BP is \" + tuple.get(\"Systolic\") + \"/\" + tuple.get(\"Diastolic\") + \".\\n\"; }) .tag(\"hypertension_stage1\") .modify(tuple -> \"High Blood Pressure (Hypertension) Stage 1\\n\" + tuple) .tag(\"hypertension_stage1\"); // Category: High Blood Pressure (Hypertension) Stage 2 TStream hypertension_stage2Alerts = hypertension_stage2 .filter(tuple -> tuple.get(\"Systolic\") >= 170 && tuple.get(\"Diastolic\") >= 105) .tag(\"hypertension_stage2\") .peek(tuple -> System.out.println(\"BP: \" + tuple.get(\"Systolic\") + \"/\" + tuple.get(\"Diastolic\"))) .map(tuple -> { return \"Warning! Monitor closely, patient
is at risk of a hypertensive crisis!\\n\"; }) .tag(\"hypertension_stage2\") .modify(tuple -> \"High Blood Pressure (Hypertension) Stage 2\\n\" + tuple) .tag(\"hypertension_stage2\"); // Category: Hypertensive Crisis TStream hypertensiveAlerts = hypertensive .filter(tuple -> tuple.get(\"Systolic\") >= 180) .tag(\"hypertensive\") .peek(tuple -> System.out.println(\"BP: \" + tuple.get(\"Systolic\") + \"/\" + tuple.get(\"Diastolic\"))) .map(tuple -> { return \"Emergency! See to patient immediately!\\n\"; }) .tag(\"hypertensive\") .modify(tuple -> tuple.toUpperCase()) .tag(\"hypertensive\") .modify(tuple -> \"Hypertensive Crisis!!!\\n\" + tuple) .tag(\"hypertensive\");```## Combining the alert streamsAt this point, we have five streams of alerts. Suppose the doctors are interested in seeing a combination of the *Normal* alerts and *Preh
ypertension* alerts. Or, suppose that they would like to see all of the alerts from all categories together. Here, `union` comes in handy. For more details about `union`, refer to the [Javadoc](http://quarks-edge.github.io/quarks/docs/javadoc/quarks/topology/TStream.html#union-quarks.topology.TStream-).There are two ways to define a union. You can either union a `TStream` with another `TStream`, or with a set of streams (`Set>`). In both cases, a single `TStream` is returned containing the tuples that flow on the input stream(s).Let's look at the first case, unioning a stream with a single stream. We can create a stream containing *Normal* alerts and *Prehypertension* alerts by unioning `normalAlerts` with `prehypertensionAlerts`.```java // Additional processing for these streams could go here. In this case, union two streams // to obtain a single stream containing alerts from the normal and prehypertension alert streams. TStream normalAndPrehypertensionAlerts = normalAlert
s.union(prehypertensionAlerts);```We can also create a stream containing alerts from all categories by looking at the other case, unioning a stream with a set of streams. We'll first create a set of `TStream` objects containing the alerts from the other three categories.```java // Set of streams containing alerts from the other categories Set> otherAlerts = new HashSet(); otherAlerts.add(hypertension_stage1Alerts); otherAlerts.add(hypertension_stage2Alerts); otherAlerts.add(hypertensiveAlerts);```We can then create an `allAlerts` stream by calling `union` on `normalAndPrehypertensionAlerts` and `otherAlerts`. `allAlerts` will contain all of the tuples from:1. `normalAlerts`2. `prehypertensionAlerts`3. `hypertension_stage1Alerts`4. `hypertension_stage2Alerts`5. `hypertensiveAlerts````java // Union a stream with a set of streams to obtain a single stream containing alerts from // all alert streams TStream allAlerts = normalAndPrehypertensionAlerts.union(otherAl
erts);```Finally, we can terminate the stream and print out all alerts.```java // Terminate the stream by printing out alerts from all categories allAlerts.sink(tuple -> System.out.println(tuple));```We end our application by submitting the `Topology`. Note that this application is available as a [sample](http://quarks-edge.github.io/quarks/docs/javadoc/quarks/samples/topology/package-summary.html).## Observing the outputWhen the final application is run, the output looks something like the following:``` BP: 176/111 High Blood Pressure (Hypertension) Stage 2 Warning! Monitor closely, patient is at risk of a hypertensive crisis! BP: 178/111 High Blood Pressure (Hypertension) Stage 2 Warning! Monitor closely, patient is at risk of a hypertensive crisis! BP: 180/110 Hypertensive Crisis!!! EMERGENCY! SEE TO PATIENT IMMEDIATELY!```## A look at the topology graphLet's see what the topology graph looks like. We can view it using the console URL that was pri
nted to standard output at the start of the application. Notice how the graph makes it easier to visualize the resulting flow of the application."
+
+},
+
+
+
+
+{
"title": "Recipe 4. Applying Different Processing Against a Single Stream",
"tags": "",
"keywords": "",
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/committers.html
----------------------------------------------------------------------
diff --git a/content/docs/committers.html b/content/docs/committers.html
index d7dc860..f3cfa5b 100644
--- a/content/docs/committers.html
+++ b/content/docs/committers.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -546,14 +555,36 @@ $('#toc').on('click', 'a', function() {
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/common-quarks-operations.html
----------------------------------------------------------------------
diff --git a/content/docs/common-quarks-operations.html b/content/docs/common-quarks-operations.html
index d9789f3..63eea4d 100644
--- a/content/docs/common-quarks-operations.html
+++ b/content/docs/common-quarks-operations.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -515,7 +524,7 @@ $('#toc').on('click', 'a', function() {
<p><br></p>
-<h4 id="changing-a-tstream-39-s-tuple-type">Changing a TStream's Tuple Type</h4>
+<h3 id="changing-a-tstream-39-s-tuple-type">Changing a TStream's Tuple Type</h3>
<p>In addition to filtering tuples, TStreams support operations that <em>transform</em> tuples from one Java type to another by invoking the TStream.map() method.</p>
@@ -539,7 +548,7 @@ $('#toc').on('click', 'a', function() {
<p><br></p>
-<h4 id="performing-stateful-operations">Performing Stateful Operations</h4>
+<h3 id="performing-stateful-operations">Performing Stateful Operations</h3>
<p>In all previous examples, the operations performed on a TStream have been stateless; keeping track of information over multiple invocations of the same operation has not been necessary. What if we want to keep track of the number of Strings sent over a stream? To do this, we need our TStream.map() method to contain a counter as state.</p>
@@ -587,14 +596,36 @@ $('#toc').on('click', 'a', function() {
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/community.html
----------------------------------------------------------------------
diff --git a/content/docs/community.html b/content/docs/community.html
index 9adaf78..6a2cbc9 100644
--- a/content/docs/community.html
+++ b/content/docs/community.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -522,7 +531,7 @@ $('#toc').on('click', 'a', function() {
<li>Contribute code, javadocs, documentation.</li>
</ul>
-<p>Visit the <a href="http://www.apache.org/foundation/getinvolved.html">Contributing</a> page and read <a href="https://github.com/apache/incubator-quarks/blob/master/DEVELOPMENT.md">DEVELOPMENT.md</a> at the top of the code tree for more information.</p>
+<p>Visit the <a href="http://www.apache.org/foundation/getinvolved.html">Contributing</a> page for general Apache contribution information. If you plan to make any significant contribution, you will need to have an Individual Contributor License Agreement <a href="https://www.apache.org/licenses/icla.txt">(ICLA)</a> on file with Apache.</p>
<h3 id="mailing-list">Mailing list</h3>
@@ -539,29 +548,43 @@ $('#toc').on('click', 'a', function() {
<h4 id="bug-reports">Bug Reports</h4>
-<p>Found bug? Enter an issue in the <a href="https://issues.apache.org/jira/browse/QUARKS">Issue Tracker</a>.</p>
+<p>Found bug? Enter an issue in <a href="https://issues.apache.org/jira/browse/QUARKS">Jira</a>.</p>
<p>Before submitting an issue, please:</p>
<ul>
<li>Verify that the bug does in fact exist.</li>
<li>Search the issue tracker to verify there is no existing issue reporting the bug you've found.</li>
-<li>Consider tracking down the bug yourself in the Quarks source and submitting apull request along with your bug report. This is a great time saver for the Quarks developers and helps ensure the bug will be fixed quickly.</li>
+<li>Consider tracking down the bug yourself in the Quarks source and submitting a pull request along with your bug report. This is a great time saver for the Quarks developers and helps ensure the bug will be fixed quickly.</li>
</ul>
<h4 id="feature-requests">Feature Requests</h4>
-<p>Enhancement requests for new features are also welcome. The more concrete and rationale the request is, the greater the chance it will incorporated into future releases.</p>
+<p>Enhancement requests for new features are also welcome. The more concrete the request is and the better rationale you provide, the greater the chance it will incorporated into future releases.</p>
<p><a href="https://issues.apache.org/jira/browse/QUARKS">https://issues.apache.org/jira/browse/QUARKS</a></p>
<h3 id="source-code">Source Code</h3>
-<p>The project sources are accessible via the <a href="https://git-wip-us.apache.org/repos/asf/incubator-quarks.git">source code repository</a> which is also mirrored in <a href="https://github.com/apache/incubator-quarks">GitHub</a></p>
+<p>The project sources are accessible via the <a href="https://git-wip-us.apache.org/repos/asf/incubator-quarks.git">source code repository</a> which is also mirrored in <a href="https://github.com/apache/incubator-quarks">GitHub</a>. </p>
+
+<p>When you are considering a code contribution, make sure there is an <a href="https://issues.apache.org/jira/browse/QUARKS">Issue</a> that describes your work or the bug you are fixing. For significant contributions, please discuss your proposed changes in the Issue so that others can comment on your plans. Someone else may be working on the same functionality, so it's good to communicate early and often. A committer is more likely to accept your change if there is clear information in the Issue. </p>
+
+<p>To contribute, <a href="https://help.github.com/articles/fork-a-repo/">fork</a> the <a href="https://github.com/apache/incubator-quarks">mirror</a> and issue a pull request. Put the Jira issue number, e.g. QUARKS-100 in the pull request title. The tag [WIP] can also be used in the title of pull requests to indicate that you are not ready to merge but want feedback. Remove [WIP] when you are ready for merge. Make sure you document your code and contribute tests along with the code.</p>
+
+<p>Read <a href="https://github.com/apache/incubator-quarks/blob/master/DEVELOPMENT.md">DEVELOPMENT.md</a> at the top of the code tree for details on setting up your development environment.</p>
-<h3 id="website-source-code">Website Source Code</h3>
+<h3 id="web-site-and-documentation-source-code">Web Site and Documentation Source Code</h3>
-<p>The project website sources are accessible via the <a href="https://git-wip-us.apache.org/repos/asf/incubator-quarks-website.git">website source code repository</a> which is also mirrored in <a href="https://github.com/apache/incubator-quarks-website">GitHub</a></p>
+<p>The project website and documentation sources are accessible via the <a href="https://git-wip-us.apache.org/repos/asf/incubator-quarks-website.git">website source code repository</a> which is also mirrored in <a href="https://github.com/apache/incubator-quarks-website">GitHub</a>. Contributing changes to the web site and documentation is similar to contributing code. Follow the instructions in the Source Code section above, but fork and issue a pull request against the <a href="https://github.com/apache/incubator-quarks-website">web site mirror</a>. Follow the instructions in the top level <a href="https://github.com/apache/incubator-quarks-website/blob/master/README.md">README.md</a> for details on contributing to the web site and documentation.</p>
+
+<p>You will need to use Markdown and Jekyll to develop pages. See:</p>
+
+<ul>
+<li><a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet">Markdown Cheat Sheet</a></li>
+<li> <a href="https://jekyllrb.com/">Jekyll on linux and Mac</a> </li>
+<li> <a href="https://jekyllrb.com/docs/windows/">Jekyll on Windows</a> is not officially supported but people have gotten it to work.</li>
+</ul>
<div class="tags">
@@ -590,14 +613,36 @@ $('#toc').on('click', 'a', function() {
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/console.html
----------------------------------------------------------------------
diff --git a/content/docs/console.html b/content/docs/console.html
index bcefcc8..ac9db9a 100644
--- a/content/docs/console.html
+++ b/content/docs/console.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -1009,14 +1018,36 @@ The bars that are the tallest and therefore have the highest tuple count are OP_
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/faq.html
----------------------------------------------------------------------
diff --git a/content/docs/faq.html b/content/docs/faq.html
index cbe7784..9e0ced8 100644
--- a/content/docs/faq.html
+++ b/content/docs/faq.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -617,14 +626,36 @@ $('#toc').on('click', 'a', function() {
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/getinvolved.html
----------------------------------------------------------------------
diff --git a/content/docs/getinvolved.html b/content/docs/getinvolved.html
deleted file mode 100644
index 93347e9..0000000
--- a/content/docs/getinvolved.html
+++ /dev/null
@@ -1,578 +0,0 @@
-<!DOCTYPE html>
- <head>
-
- <meta charset="utf-8">
-<meta http-equiv="X-UA-Compatible" content="IE=edge">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<meta name="description" content="">
-<meta name="keywords" content=" ">
-<title>Get Involved | Quarks Documentation</title>
-<link rel="stylesheet" type="text/css" href="../css/syntax.css">
-<link rel="stylesheet" type="text/css" href="../css/font-awesome.min.css">
-<!--<link rel="stylesheet" type="text/css" href="../css/bootstrap.min.css">-->
-<link rel="stylesheet" type="text/css" href="../css/modern-business.css">
-<link rel="stylesheet" type="text/css" href="../css/lavish-bootstrap.css">
-<link rel="stylesheet" type="text/css" href="../css/customstyles.css">
-<link rel="stylesheet" type="text/css" href="../css/theme-blue.css">
-<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js"></script>
-<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery-cookie/1.4.1/jquery.cookie.min.js"></script>
-<script src="../js/jquery.navgoco.min.js"></script>
-<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js"></script>
-<script src="https://cdnjs.cloudflare.com/ajax/libs/anchor-js/2.0.0/anchor.min.js"></script>
-<script src="../js/toc.js"></script>
-<script src="../js/customscripts.js"></script>
-<link rel="shortcut icon" href="../common_images/favicon.ico" type="image/x-icon">
-<!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->
-<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
-<!--[if lt IE 9]>
-<script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
-<script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script>
-<![endif]-->
-
-
-
-
-
-
-
-
-
-<script>
- $(function () {
- $('[data-toggle="tooltip"]').tooltip()
- })
-</script>
-
-
-
- </head>
-
-<body>
-
- <!-- Navigation -->
-<nav class="navbar navbar-inverse navbar-fixed-top" role="navigation">
- <div class="container topnavlinks">
- <div class="navbar-header">
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- <a class="fa fa-home fa-lg navbar-brand" href="home.html"> <span class="projectTitle"> Quarks Documentation</span></a>
-
- </div>
- <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
- <ul class="nav navbar-nav navbar-right">
- <!-- entries without drop-downs appear here -->
- <!-- conditional logic to control which topnav appears for the audience defined in the configuration file.-->
-
-
-
-
-
-
-
-
-
- <li class="dropdown">
-
-
-
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Github Repos<b class="caret"></b></a>
- <ul class="dropdown-menu">
-
-
-
- <li><a href="https://github.com/apache/incubator-quarks" target="_blank">Source code</a></li>
-
-
-
-
-
- <li><a href="https://github.com/apache/incubator-quarks-website" target="_blank">Website/Documentation</a></li>
-
-
-
-
-
- </ul>
- </li>
-
-
-
-
-
-
-
-
- <li><a href="https://quarks-edge.github.io/quarks/docs/javadoc/index.html" target="_blank">Javadoc</a></li>
-
-
-
-
-
-
- <!-- entries with drop-downs appear here -->
- <!-- conditional logic to control which topnav appears for the audience defined in the configuration file.-->
-
- <li class="dropdown">
-
-
-
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Quarks Resources<b class="caret"></b></a>
- <ul class="dropdown-menu">
-
-
-
- <li><a href="https://github.com/apache/incubator-quarks/releases" target="_blank">Download</a></li>
-
-
-
-
-
- <li><a href="samples">Samples</a></li>
-
-
-
-
-
- <li><a href="faq">FAQ</a></li>
-
-
-
-
-
- </ul>
- </li>
-
-
-
-
- <!-- special insertion -->
-
-
- <!-- Send feedback function -->
-<script>
-function SendLinkByMail(href) {
-var subject= "Quarks Documentation feedback";
-var body = "I have some feedback about the Get Involved page: ";
-body += window.location.href;
-body += "";
-var uri = "mailto:?subject=";
-uri += encodeURIComponent(subject);
-uri += "&body=";
-uri += encodeURIComponent(body);
-window.location.href = uri;
-}
-</script>
-
-<li><a href="mailto:dev@quarks.incubator.apache.org" target="_blank"><i class="fa fa-envelope-o"></i> Feedback</a></li>
-
-
- <!--uncomment this block if you want simple search instead of algolia-->
- <li>
- <!--start search-->
- <div id="search-demo-container">
- <input type="text" id="search-input" placeholder="search...">
- <ul id="results-container"></ul>
- </div>
- <script src="../js/jekyll-search.js" type="text/javascript"></script>
- <script type="text/javascript">
- SimpleJekyllSearch.init({
- searchInput: document.getElementById('search-input'),
- resultsContainer: document.getElementById('results-container'),
- dataSource: '../search.json',
- searchResultTemplate: '<li><a href="{url}" title="Get Involved">{title}</a></li>',
- noResultsText: 'No results found.',
- limit: 10,
- fuzzy: true,
- })
- </script>
- <!--end search-->
- </li>
-
-
- </div>
- <!-- /.container -->
-</nav>
-
-
- <!-- Page Content -->
- <div class="container">
- <div class="col-lg-12"> </div>
-
-
-<!-- Content Row -->
-<div class="row">
- <!-- Sidebar Column -->
- <div class="col-md-3">
-
- <script>
-
- $(document).ready(function() {
- // Initialize navgoco with default options
- $("#mysidebar").navgoco({
- caretHtml: '',
- accordion: true,
- openClass: 'active', // open
- save: false, // leave false or nav highlighting doesn't work right
- cookie: {
- name: 'navgoco',
- expires: false,
- path: '/'
- },
- slide: {
- duration: 400,
- easing: 'swing'
- }
- });
-
- $("#collapseAll").click(function(e) {
- e.preventDefault();
- $("#mysidebar").navgoco('toggle', false);
- });
-
- $("#expandAll").click(function(e) {
- e.preventDefault();
- $("#mysidebar").navgoco('toggle', true);
- });
-
- });
-
- </script>
-
-
-
-
-
-
-
-
-
-
-
-
- <ul id="mysidebar" class="nav">
-
- <span class="siteTagline">Quarks</span>
- <span class="versionTagline">Version 0.3.0</span>
-
-
-
-
-
-
- <li><a href="#">Overview</a>
- <ul>
-
-
-
- <li><a href="../docs/quarks_index.html">Introduction</a></li>
-
-
-
-
-
-
-
-
- <li><a href="../docs/faq.html">FAQ</a></li>
-
-
-
-
-
-
- </ul>
-
-
-
- <li><a href="#">Get Started</a>
- <ul>
-
-
-
- <li><a href="../docs/quarks-getting-started.html">1. Getting Started Guide</a></li>
-
-
-
-
-
-
-
-
- <li><a href="../docs/common-quarks-operations.html">2. Common Operations</a></li>
-
-
-
-
-
-
- </ul>
-
-
-
- <li><a href="#">Quarks Cookbook</a>
- <ul>
-
-
-
- <li><a href="../recipes/recipe_hello_quarks.html">Recipe 1. Hello Quarks!</a></li>
-
-
-
-
-
-
-
-
- <li><a href="../recipes/recipe_source_function.html">Recipe 2. Writing a Source Function</a></li>
-
-
-
-
-
-
-
-
- <li><a href="../recipes/recipe_value_out_of_range.html">Recipe 3. Detecting a Sensor Value Out of Expected Range</a></li>
-
-
-
-
-
-
-
-
- <li><a href="../recipes/recipe_different_processing_against_stream.html">Recipe 4. Applying Different Processing Against a Single Stream</a></li>
-
-
-
-
-
-
- </ul>
-
-
-
- <li><a href="#">Sample Programs</a>
- <ul>
-
-
-
- <li><a href="../docs/samples.html">1. Samples</a></li>
-
-
-
-
-
-
-
-
- <li><a href="../docs/quickstart.html">2. Quickstart IBM Watson IoT Platform</a></li>
-
-
-
-
-
-
- </ul>
-
-
-
- <li><a href="#">Using The Console</a>
- <ul>
-
-
-
- <li><a href="../docs/console.html">1. Using The Console</a></li>
-
-
-
-
-
-
- </ul>
-
-
-
- <li><a href="#">Get involved</a>
- <ul>
-
-
-
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
-
-
-
-
-
-
-
-
- <li><a href="../docs/committers.html">Committers</a></li>
-
-
-
-
-
-
- </ul>
-
-
-
-
-
- <!-- if you aren't using the accordion, uncomment this block:
-
- <p class="external">
- <a href="#" id="collapseAll">Collapse All</a> | <a href="#" id="expandAll">Expand All</a>
- </p>
- -->
- <br/>
- </li>
- </ul>
- <div class="row">
- <div class="col-md-12">
-
-<!-- this handles the automatic toc. use ## for subheads to auto-generate the on-page minitoc. if you use html tags, you must supply an ID for the heading element in order for it to appear in the minitoc. -->
-<script>
-$( document ).ready(function() {
- // Handler for .ready() called.
-
-$('#toc').toc({ minimumHeaders: 0, listType: 'ul', showSpeed: 0, headers: 'h2,h3,h4' });
-
-/* this offset helps account for the space taken up by the floating toolbar. */
-$('#toc').on('click', 'a', function() {
- var target = $(this.getAttribute('href'))
- , scroll_target = target.offset().top
-
- $(window).scrollTop(scroll_target - 10);
- return false
-})
-
-});
-</script>
-
-
-<div id="toc"></div>
-
- </div>
- </div>
- </div>
-
- <!-- this highlights the active parent class in the navgoco sidebar. this is critical so that the parent expands when you're viewing a page. This must appear below the sidebar code above. Otherwise, if placed inside customscripts.js, the script runs before the sidebar code runs and the class never gets inserted.-->
- <script>$("li.active").parents('li').toggleClass("active");</script>
-
-
- <!-- Content Column -->
- <div class="col-md-9">
-
- <div class="post-header">
- <h1 class="post-title-main">Get Involved</h1>
-</div>
-
-<div class="post-content">
-
-
-
-<!-- this handles the automatic toc. use ## for subheads to auto-generate the on-page minitoc. if you use html tags, you must supply an ID for the heading element in order for it to appear in the minitoc. -->
-<script>
-$( document ).ready(function() {
- // Handler for .ready() called.
-
-$('#toc').toc({ minimumHeaders: 0, listType: 'ul', showSpeed: 0, headers: 'h2,h3,h4' });
-
-/* this offset helps account for the space taken up by the floating toolbar. */
-$('#toc').on('click', 'a', function() {
- var target = $(this.getAttribute('href'))
- , scroll_target = target.offset().top
-
- $(window).scrollTop(scroll_target - 10);
- return false
-})
-
-});
-</script>
-
-
-<div id="toc"></div>
-
-
-
-
- <a target="_blank" href="https://github.com/apache/incubator-quarks-website/blob/master/site/docs/getinvolved.md" class="btn btn-default githubEditButton" role="button"><i class="fa fa-github fa-lg"></i> Edit me</a>
-
- <h1 id="get-involved-with-quarks">Get Involved with Quarks</h1>
-
-<p>Welcome to the Quarks community! We would love to have you participate as a user of Quarks, a contributor or both.</p>
-
-<h2 id="contribute-code">Contribute Code</h2>
-
-<p>If you plan to make any significant contribution, you will need to have a Contributor License Agreement <a href="https://github.com/quarks-edge/quarks/blob/master/licences/Quarks-cla-individual.pdf">(CLA)</a> on file. Get a copy of the CLA, fill it out and follow the instructions in the CLA to file it. Committers will require a CLA before they commit contributions.</p>
-
-<p>When you are considering a code contribution, make sure there is an <a href="https://github.com/quarks-edge/quarks/issues">Issue</a> that describes your work or the bug you are fixing. For significant contributions, please discuss your proposed changes in the Issue so that others can comment on your plans. Someone else may be working on the same functionality, so it's good to communicate early and often. A committer is more likely to accept your change if there is clear information in the Issue. </p>
-
-<p>The best way to start on the code is to <a href="https://help.github.com/articles/fork-a-repo/">fork</a> Quarks and make changes in your fork. When you're happy with the changes in your fork, issue a <a href="https://github.com/quarks-edge/quarks/pulls">pull request</a>. Make sure you document your code and contribute tests along with the code.</p>
-
-<p>We welcome new committers. Get information on committers <a href="committers">here</a>.</p>
-
-<h2 id="contribute-documentation-for-the-web-site">Contribute Documentation for the Web Site</h2>
-
-<p>Contributing documentation is similar to contributing code. Follow the instructions in the Contribute Code Section above. If you are submitting documentation for the web site, you will need to use Markdown and Jekyll to develop your web pages.</p>
-
-<ul>
-<li><a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet">Markdown Cheat Sheet</a></li>
-<li><a href="https://help.github.com/articles/using-jekyll-with-pages/">Using Jekyll with Pages</a></li>
-</ul>
-
-<h2 id="use-quarks-and-participate-in-the-community">Use Quarks and Participate in the Community</h2>
-
-<p>Please <a href="https://github.com/quarks-edge/quarks/releases/latest">download</a> the latest release of Quarks and use it. We would love to get your feedback. Create an <a href="https://github.com/quarks-edge/quarks/issues">Issue</a> for any bugs you encounter, requests for enhancements or questions you may have. Feel free to comment on existing issues as well. You are welcome to update the <a href="https://github.com/quarks-edge/quarks/wiki">wiki</a> with any information you want to provide to help others. Just link in any new pages, to be sure they are not lost. If you have any significant comments on existing wiki pages, open an Issue to have a discussion.</p>
-
-
-<div class="tags">
-
-</div>
-
-<!--
-
- <div id="disqus_thread"></div>
- <script type="text/javascript">
- /* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
- var disqus_shortname = 'idrbwjekyll'; // required: replace example with your forum shortname
-
- /* * * DON'T EDIT BELOW THIS LINE * * */
- (function() {
- var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
- dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
- (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
- })();
- </script>
- <noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
- -->
-
-</div>
-
-
-
-<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
-
- </div>
- </div>
-</footer>
- </div><!-- /.row -->
-
- </div> <!-- /.container -->
-
-</body>
-
-
-</html>
-
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/home.html
----------------------------------------------------------------------
diff --git a/content/docs/home.html b/content/docs/home.html
index bd949f1..c0ba340 100644
--- a/content/docs/home.html
+++ b/content/docs/home.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -622,14 +631,36 @@ medical device.</li>
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/overview.html
----------------------------------------------------------------------
diff --git a/content/docs/overview.html b/content/docs/overview.html
index 70e6f11..0a13750 100644
--- a/content/docs/overview.html
+++ b/content/docs/overview.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -606,14 +615,36 @@ medical device.</li>
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/b72be05e/content/docs/quarks-getting-started.html
----------------------------------------------------------------------
diff --git a/content/docs/quarks-getting-started.html b/content/docs/quarks-getting-started.html
index 56ab6fd..18bc968 100644
--- a/content/docs/quarks-getting-started.html
+++ b/content/docs/quarks-getting-started.html
@@ -353,6 +353,15 @@ window.location.href = uri;
+
+
+ <li><a href="../recipes/recipe_combining_streams_processing_results.html">Recipe 5. Splitting a Stream to Apply Different Processing and Combining the Results into a Single Stream</a></li>
+
+
+
+
+
+
</ul>
@@ -403,7 +412,7 @@ window.location.href = uri;
- <li><a href="../docs/getinvolved.html">How to participate</a></li>
+ <li><a href="../docs/community.html">How to participate</a></li>
@@ -708,14 +717,36 @@ Your environment is set up! You can start writing your first Quarks application.
<footer>
- <div class="row">
- <div class="col-lg-12 footer">
-
- Site last generated: Mar 23, 2016 <br />
+ <div class="row">
+ <div class="col-lg-12 footer">
- </div>
- </div>
+ Site last
+ generated: Mar 29, 2016 <br/>
+
+ </div>
+ </div>
+ <br/>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
+ until a further review indicates that the infrastructure, communications, and decision making process
+ have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the
+ project has yet to be fully endorsed by the ASF.</p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-12">
+ <p class="small">Copyright © 2016 The Apache Software Foundation. Licensed under the Apache
+ License, Version 2.0.
+ Apache, the Apache Feather logo, and the Apache Incubator project logo are trademarks of The Apache
+ Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their
+ respective owners.</p>
+ </div>
+ </div>
</footer>
+
</div><!-- /.row -->
</div> <!-- /.container -->