You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@apex.apache.org by an...@apache.org on 2017/11/12 02:26:04 UTC
[apex-site] branch asf-site updated: from
39ea2e43c6cdc904291018341b55f375005336e3
This is an automated email from the ASF dual-hosted git repository.
ananthg pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/apex-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f812a72 from 39ea2e43c6cdc904291018341b55f375005336e3
f812a72 is described below
commit f812a7200437fa67f69ddf4f16798d05c2d9a050
Author: Apex Dev <de...@apex.apache.org>
AuthorDate: Sun Nov 12 13:25:34 2017 +1100
from 39ea2e43c6cdc904291018341b55f375005336e3
---
content/docs/malhar | 2 +-
content/downloads.html | 118 +++++++++++--------------------------------------
content/roadmap.html | 86 +++++++++++++++++------------------
3 files changed, 70 insertions(+), 136 deletions(-)
diff --git a/content/docs/malhar b/content/docs/malhar
index 958582c..4d3f6aa 120000
--- a/content/docs/malhar
+++ b/content/docs/malhar
@@ -1 +1 @@
-malhar-3.7
\ No newline at end of file
+malhar-3.8
\ No newline at end of file
diff --git a/content/downloads.html b/content/downloads.html
index f011327..e518b34 100644
--- a/content/downloads.html
+++ b/content/downloads.html
@@ -110,7 +110,7 @@
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2017-05-04
+ 2017-05-05
</td>
<td>
<a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-core-3.6.0/apache-apex-core-3.6.0-source-release.zip">apex-3.6.0-source-release.zip</a><br>
@@ -143,7 +143,7 @@
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2016-12-10
+ 2016-12-11
</td>
<td>
<a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-core-3.5.0/apache-apex-core-3.5.0-source-release.zip">apex-3.5.0-source-release.zip</a><br>
@@ -186,136 +186,70 @@
</tr>
</thead>
<tbody>
- <tr>
- <td>
- 3.8.0
- <span class="latest-tag">(latest)</span>
- </td>
- <td>
- 2017-11-11
- </td>
- <td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip">malhar-3.8.0-source-release.zip</a><br>
- <small>
- (
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip.sha512">sha512</a>
- )
- </small>
- </td>
- <td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz">malhar-3.8.0-source-release.tar.gz</a><br>
- <small>
- (
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz.sha512">sha512</a>
- )
- </small>
- </td>
- <td>
- <a href="/docs/malhar-3.8">user documentation</a><br>
- <a href="https://ci.apache.org/projects/apex-malhar/apex-malhar-javadoc-release-3.8/index.html">javadoc</a><br>
- </td>
- </tr>
- <tr>
- <td>
- 3.7.0
- <span class="latest-tag">(latest)</span>
- </td>
- <td>
- 2017-03-31
- </td>
- <td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip">malhar-3.7.0-source-release.zip</a><br>
- <small>
- (
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip.sha">sha1</a>
- )
- </small>
- </td>
- <td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz">malhar-3.7.0-source-release.tar.gz</a><br>
- <small>
- (
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz.sha">sha1</a>
- )
- </small>
- </td>
- <td>
- <a href="/docs/malhar-3.7">user documentation</a><br>
- <a href="https://ci.apache.org/projects/apex-malhar/apex-malhar-javadoc-release-3.7/index.html">javadoc</a><br>
- </td>
- </tr>
<tr>
<td>
- 3.6.0
+ 3.8.0
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2016-12-02
+ 2017-11-12
</td>
<td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.zip">malhar-3.6.0-source-release.zip</a><br>
+ <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip">malhar-3.8.0-source-release.zip</a><br>
<small>
(
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.zip.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.zip.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.zip.sha">sha1</a>
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip.asc">pgp</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip.md5">md5</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.zip.sha">sha1</a>
)
</small>
</td>
<td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.tar.gz">malhar-3.6.0-source-release.tar.gz</a><br>
+ <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz">malhar-3.8.0-source-release.tar.gz</a><br>
<small>
(
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.tar.gz.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.tar.gz.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.6.0/apache-apex-malhar-3.6.0-source-release.tar.gz.sha">sha1</a>
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz.asc">pgp</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz.md5">md5</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.8.0/apache-apex-malhar-3.8.0-source-release.tar.gz.sha">sha1</a>
)
</small>
</td>
<td>
- <a href="/docs/malhar-3.6">user documentation</a><br>
- <a href="https://ci.apache.org/projects/apex-malhar/apex-malhar-javadoc-release-3.6/index.html">javadoc</a><br>
+ <a href="/docs/malhar-3.8">user documentation</a><br>
+ <a href="https://ci.apache.org/projects/apex-malhar/apex-malhar-javadoc-release-3.8/index.html">javadoc</a><br>
</td>
</tr>
<tr>
<td>
- 3.5.0
+ 3.7.0
<span class="latest-tag">(latest)</span>
</td>
<td>
- 2016-09-03
+ 2017-04-01
</td>
<td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.zip">malhar-3.5.0-source-release.zip</a><br>
+ <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip">malhar-3.7.0-source-release.zip</a><br>
<small>
(
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.zip.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.zip.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.zip.sha">sha1</a>
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip.asc">pgp</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip.md5">md5</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.zip.sha">sha1</a>
)
</small>
</td>
<td>
- <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.tar.gz">malhar-3.5.0-source-release.tar.gz</a><br>
+ <a href="http://www.apache.org/dyn/closer.lua/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz">malhar-3.7.0-source-release.tar.gz</a><br>
<small>
(
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.tar.gz.asc">pgp</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.tar.gz.md5">md5</a>,
- <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.5.0/apache-apex-malhar-3.5.0-source-release.tar.gz.sha">sha1</a>
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz.asc">pgp</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz.md5">md5</a>,
+ <a href="https://dist.apache.org/repos/dist/release/apex/apache-apex-malhar-3.7.0/apache-apex-malhar-3.7.0-source-release.tar.gz.sha">sha1</a>
)
</small>
</td>
<td>
- <a href="/docs/malhar-3.5">user documentation</a><br>
- <a href="https://ci.apache.org/projects/apex-malhar/apex-malhar-javadoc-release-3.5/index.html">javadoc</a><br>
+ <a href="/docs/malhar-3.7">user documentation</a><br>
+ <a href="https://ci.apache.org/projects/apex-malhar/apex-malhar-javadoc-release-3.7/index.html">javadoc</a><br>
</td>
</tr>
</tbody>
diff --git a/content/roadmap.html b/content/roadmap.html
index 0549ac6..2180124 100644
--- a/content/roadmap.html
+++ b/content/roadmap.html
@@ -108,10 +108,10 @@
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXCORE-231">APEXCORE-231</a>
</td>
- <td title="The Apex engine supports many platform level attributes like operator memory, application window count, container jvm options etc. Today these can only be set at application launch time and cannot be changed once the application is running.
-
-This issue is to add the ability to change the attributes dynamically even as the application is running. The mechanics of an user requesting the attribute change can be similar to how a user requests property change via the command line client.
-
+ <td title="The Apex engine supports many platform level attributes like operator memory, application window count, container jvm options etc. Today these can only be set at application launch time and cannot be changed once the application is running.
+
+This issue is to add the ability to change the attributes dynamically even as the application is running. The mechanics of an user requesting the attribute change can be similar to how a user requests property change via the command line client.
+
Since each attribute is different the actual backend implementation to affect the changes will most likely be custom handling for different attributes but during the implementation process hopefully some common themes emerge and some amount of reuse possible.">
Ability to change attributes at runtime
</td>
@@ -124,12 +124,12 @@ Since each attribute is different the actual backend implementation to affect th
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXCORE-232">APEXCORE-232</a>
</td>
- <td title="There are scenarios when new processing code needs to be added to an already running application. There are two scenarios.
-
-a. A bug is discovered in an operator and an existing operator in the running DAG needs to be replaced. The platform supports shutting down and resuming an application which could be use as a first cut way to do this but there are a couple of drawbacks.
- i. This only works when the input source has memory, if it doesn't the messages received during the time the application is down are lost.
- ii. Depending on the complexity and state of the application it may take some time for this entire process and the application to get back to running state and this delay may not be acceptable for the downstream components that depend on the output of this application.
-
+ <td title="There are scenarios when new processing code needs to be added to an already running application. There are two scenarios.
+
+a. A bug is discovered in an operator and an existing operator in the running DAG needs to be replaced. The platform supports shutting down and resuming an application which could be use as a first cut way to do this but there are a couple of drawbacks.
+ i. This only works when the input source has memory, if it doesn't the messages received during the time the application is down are lost.
+ ii. Depending on the complexity and state of the application it may take some time for this entire process and the application to get back to running state and this delay may not be acceptable for the downstream components that depend on the output of this application.
+
b. A new operator needs to be added to the DAG to take data from an existing operator and do some additional processing. Today this is supported as long as the code for the operator is already in the application libraries. Often this will not be the case as users will not know what the operator will be beforehand when the application is originally launched.">
Ability to add new processing code to the DAG
</td>
@@ -142,14 +142,14 @@ b. A new operator needs to be added to the DAG to take data from an existing ope
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXCORE-234">APEXCORE-234</a>
</td>
- <td title="The current property file specification follows the hadoop configuration file format and this has led to some drawbacks.
- a. The names for the properties and attributes are verbose in the configuration file.
- b. When there are nested properties in operators the syntax deviates from the bean specification because it introduces some specific keywords in the specification like .prop and ,attr.
-
-There will already be some changes afoot based on the following
- a. When adding ability to specify single instance attributes (https://malhar.atlassian.net/browse/APEXCORE-233) implementing it in the current syntax may not be possible or lead to very unwieldy syntax.
- b. There are also other ideas such as one from David to have the ability to specify global application level attributes which possible require rethinking the current syntax.
-
+ <td title="The current property file specification follows the hadoop configuration file format and this has led to some drawbacks.
+ a. The names for the properties and attributes are verbose in the configuration file.
+ b. When there are nested properties in operators the syntax deviates from the bean specification because it introduces some specific keywords in the specification like .prop and ,attr.
+
+There will already be some changes afoot based on the following
+ a. When adding ability to specify single instance attributes (https://malhar.atlassian.net/browse/APEXCORE-233) implementing it in the current syntax may not be possible or lead to very unwieldy syntax.
+ b. There are also other ideas such as one from David to have the ability to specify global application level attributes which possible require rethinking the current syntax.
+
Users have also asked for an easier and more consistent way to specify these properties. This issue is to track the ideas and progress of these changes.">
Better application configuration specification
</td>
@@ -174,11 +174,11 @@ Users have also asked for an easier and more consistent way to specify these pro
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXCORE-289">APEXCORE-289</a>
</td>
- <td title="We should support encrypted streams in a DAG for Apex.
-Basically there will be 2 ways user can configure the streams for encryption:
-1) App wide attributes- Using which all the stream in the DAG will have encrypted channel.
-2) Stream based attribute - Using this user can set a certain stream to flow over encrypted channel.
-
+ <td title="We should support encrypted streams in a DAG for Apex.
+Basically there will be 2 ways user can configure the streams for encryption:
+1) App wide attributes- Using which all the stream in the DAG will have encrypted channel.
+2) Stream based attribute - Using this user can set a certain stream to flow over encrypted channel.
+
Encrypted for the streams should done at Network/Buffer Server levels.">
Encrypted Streams in Apex DAG
</td>
@@ -191,17 +191,17 @@ Encrypted for the streams should done at Network/Buffer Server levels.">
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXCORE-418">APEXCORE-418</a>
</td>
- <td title="Today Apex has two modes of execution: Embedded mode (everything running in a single JVM) and YARN. There has been a few questions around native support for Mesos. A cursory look suggests that Mesos support can be added by reimplementing the YARN specific portions in the master (AppMasterService, ContainerLauncher) and limited changes to the streaming container driver.
-
-Mesos has a different model of resource allocation: The master offers resources to the framework while in YARN resources are requested. Apex master needs to implement the "framework scheduler" that is responsible to accept the resources and control the tasks.
-
-http://mesos.apache.org/documentation/latest/app-framework-development-guide/
-
-Tasks are launched through executors, command line and docker executors are provided.
-
-Apex also requires support to deploy the dependencies to the nodes on which the streaming containers are launched. YARN supports that through resource localization. Mesos supports this through the fetcher, which can copy the resources to the slave node.
-
-http://mesos.apache.org/documentation/latest/fetcher/
+ <td title="Today Apex has two modes of execution: Embedded mode (everything running in a single JVM) and YARN. There has been a few questions around native support for Mesos. A cursory look suggests that Mesos support can be added by reimplementing the YARN specific portions in the master (AppMasterService, ContainerLauncher) and limited changes to the streaming container driver.
+
+Mesos has a different model of resource allocation: The master offers resources to the framework while in YARN resources are requested. Apex master needs to implement the "framework scheduler" that is responsible to accept the resources and control the tasks.
+
+http://mesos.apache.org/documentation/latest/app-framework-development-guide/
+
+Tasks are launched through executors, command line and docker executors are provided.
+
+Apex also requires support to deploy the dependencies to the nodes on which the streaming containers are launched. YARN supports that through resource localization. Mesos supports this through the fetcher, which can copy the resources to the slave node.
+
+http://mesos.apache.org/documentation/latest/fetcher/
">
Support for Mesos
</td>
@@ -252,9 +252,9 @@ http://mesos.apache.org/documentation/latest/fetcher/
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-1999">APEXMALHAR-1999</a>
</td>
- <td title="Flink streaming is compatible with Apache Storm interfaces and therefore allows reusing code that was implemented for Storm.
-Details can be found here.
-https://ci.apache.org/projects/flink/flink-docs-master/apis/storm_compatibility.html
+ <td title="Flink streaming is compatible with Apache Storm interfaces and therefore allows reusing code that was implemented for Storm.
+Details can be found here.
+https://ci.apache.org/projects/flink/flink-docs-master/apis/storm_compatibility.html
This jira item can contain tasks for providing similar support in Apex">
Running a Storm topology on Apex.
</td>
@@ -267,9 +267,9 @@ This jira item can contain tasks for providing similar support in Apex">
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-2260">APEXMALHAR-2260</a>
</td>
- <td title="Support execution of Python code in an operator.
-
-https://lists.apache.org/thread.html/9837b1dee8f909ed400c6030ce5c6a94a12f43183718019dd0bfd228@%3Cdev.apex.apache.org%3E
+ <td title="Support execution of Python code in an operator.
+
+https://lists.apache.org/thread.html/9837b1dee8f909ed400c6030ce5c6a94a12f43183718019dd0bfd228@%3Cdev.apex.apache.org%3E
">
Python execution for operator logic
</td>
@@ -282,9 +282,9 @@ https://lists.apache.org/thread.html/9837b1dee8f909ed400c6030ce5c6a94a12f4318371
<td>
<a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-2261">APEXMALHAR-2261</a>
</td>
- <td title="A high level API similar to the Apex Java stream API that lets users specify an application in Python.
-
-https://lists.apache.org/thread.html/9837b1dee8f909ed400c6030ce5c6a94a12f43183718019dd0bfd228@%3Cdev.apex.apache.org%3E
+ <td title="A high level API similar to the Apex Java stream API that lets users specify an application in Python.
+
+https://lists.apache.org/thread.html/9837b1dee8f909ed400c6030ce5c6a94a12f43183718019dd0bfd228@%3Cdev.apex.apache.org%3E
">
Python binding for high level API
</td>
--
To stop receiving notification emails like this one, please contact
['"commits@apex.apache.org" <co...@apex.apache.org>'].