Repository: apex-site Updated Branches: refs/heads/asf-site 61a09b7f9 -> d86c144d2
from 2639c0c9a16a3acb184f6f163a49837f52e8922d Project: http://git-wip-us.apache.org/repos/asf/apex-site/repo Commit: http://git-wip-us.apache.org/repos/asf/apex-site/commit/d86c144d Tree: http://git-wip-us.apache.org/repos/asf/apex-site/tree/d86c144d Diff: http://git-wip-us.apache.org/repos/asf/apex-site/diff/d86c144d Branch: refs/heads/asf-site Commit: d86c144d2dfe46d57e3ff86d342111dc056bc038 Parents: 61a09b7 Author: Thomas Weise <[email protected]> Authored: Wed Aug 17 15:22:30 2016 -0700 Committer: Thomas Weise <[email protected]> Committed: Wed Aug 17 15:22:30 2016 -0700 ---------------------------------------------------------------------- content/roadmap.html | 79 +++++++++++------------------------------------ 1 file changed, 18 insertions(+), 61 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/apex-site/blob/d86c144d/content/roadmap.html ---------------------------------------------------------------------- diff --git a/content/roadmap.html b/content/roadmap.html index 1ee8ecd..8371f65 100644 --- a/content/roadmap.html +++ b/content/roadmap.html @@ -343,50 +343,6 @@ So keep things sane - the proposed compromise is that we start creating smaller </tr> <tr> <td> - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-1897";>APEXMALHAR-1897</a> - </td> - <td title="ManagedState is described in the document below: - -https://docs.google.com/document/d/1gRWN9ufKSZSZD0N-pthlhpC9TZ8KwJ6hJlAX6nxl5f8/edit#heading=h.z87ti1fwyt0t";> - Large operator state management - </td> - <td> - - - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR/fixforversion/12334637";>3.4.0</a> - - - </td> - </tr> - <tr> - <td> - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-1938";>APEXMALHAR-1938</a> - </td> - <td title="Currently Apex engine provides operator checkpointing in Hdfs ( with Hdfs backed StorageAgents i.e. FSStorageAgent & AsyncFSStorageAgent ) -As operator check-pointing is critical functionality of Apex streaming platform to ensure fault tolerant behavior, platform should also provide alternate StorageAgents which will work seamlessly with large applications that requires Exactly once semantics. -HDFS read/write latency is limited and doesn't improve beyond certain point because of disk io & staging writes. Having alternate strategy to this check-pointing in fault tolerant distributed in-memory grid would ensure application stability and performance is not impacted by checkpointing - -*This feature will add below functionalities* -* A KeyValue store interface which is used by In-memory checkpointing storage agent. -* Abstract implementation of KeyValue storage agent which can be configured with concrete implementation of KeyValue store for checkpointing. -* Concrete implementation of In memory storage agent for Apache Geode - -*This feature depends on below APEX core feature* -https://issues.apache.org/jira/browse/APEXCORE-283 -* Interface for storage agent to provide application id -* Stram client changes to pass applicationId"> - Operator checkpointing in distributed in-memory store - </td> - <td> - - - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR/fixforversion/12334637";>3.4.0</a> - - - </td> - </tr> - <tr> - <td> <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-1939";>APEXMALHAR-1939</a> </td> <td title=""> @@ -399,23 +355,6 @@ https://issues.apache.org/jira/browse/APEXCORE-283 </tr> <tr> <td> - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-1942";>APEXMALHAR-1942</a> - </td> - <td title="We would like to contribute the Apache Geode(http://geode.incubator.apache.org/) Operator support for Apex. -It will basically be implementation for writing to geode region. -This is in continuation with the Operator checkpointing alternative under review (MLHR-1938)"> - Apex Operator for Apache Geode. - </td> - <td> - - - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR/fixforversion/12334637";>3.4.0</a> - - - </td> - </tr> - <tr> - <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. @@ -453,6 +392,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/fixforversion/12335815";>3.5.0</a> + + </td> </tr> <tr> @@ -468,6 +410,21 @@ This jira item can contain tasks for providing similar support in Apex"> </td> </tr> + <tr> + <td> + <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-2142";>APEXMALHAR-2142</a> + </td> + <td title=""> + High-level API window support + </td> + <td> + + + <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR/fixforversion/12335815";>3.5.0</a> + + + </td> + </tr> </tbody> </table>
