Repository: apex-site Updated Branches: refs/heads/asf-site 029c6d054 -> f005b2595
from 2a37a06fe554438c6bd9535d724e0ef6cb990049 Project: http://git-wip-us.apache.org/repos/asf/apex-site/repo Commit: http://git-wip-us.apache.org/repos/asf/apex-site/commit/f005b259 Tree: http://git-wip-us.apache.org/repos/asf/apex-site/tree/f005b259 Diff: http://git-wip-us.apache.org/repos/asf/apex-site/diff/f005b259 Branch: refs/heads/asf-site Commit: f005b259505f5ea7cb58eca0900589e9d48c8c10 Parents: 029c6d0 Author: Thomas Weise <[email protected]> Authored: Wed Sep 28 20:27:40 2016 -0700 Committer: Thomas Weise <[email protected]> Committed: Wed Sep 28 20:27:40 2016 -0700 ---------------------------------------------------------------------- content/roadmap.html | 24 ------------------------ 1 file changed, 24 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/apex-site/blob/f005b259/content/roadmap.html ---------------------------------------------------------------------- diff --git a/content/roadmap.html b/content/roadmap.html index 5bee01a..6062a03 100644 --- a/content/roadmap.html +++ b/content/roadmap.html @@ -242,18 +242,6 @@ Encrypted for the streams should done at Network/Buffer Server levels."> </tr> <tr> <td> - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXCORE-414";>APEXCORE-414</a> - </td> - <td title="Apex core has streaming windows that establish a boundary based on arrival time of events. Many applications require boundaries based on the time of events, which could be a field in the tuple. Some of the operators support this today (time bucketing), but it would be good to provide more generic support for this in the engine itself. "> - Native support for event-time windowing - </td> - <td> - - - </td> - </tr> - <tr> - <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. @@ -321,18 +309,6 @@ All checkpoints that happened before the committed window is deleted but the nam <tbody> <tr> <td> - <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-1720";>APEXMALHAR-1720</a> - </td> - <td title=""> - Development of Inner Join Operator - </td> - <td> - - - </td> - </tr> - <tr> - <td> <a target="_blank" href="https://issues.apache.org/jira/browse/APEXMALHAR-1811";>APEXMALHAR-1811</a> </td> <td title="Add new condition for non-equality join predicate (for example, user.zipcode != authzn.zipcode)">
