[beam-site] 01/03: Capabilities Matrix: Stateful processing support in Apex Runner

[al...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

altay pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam-site.git

commit e6dfdd3cd81db509ca4af1507600b3eec147cd26
Author: Thomas Weise <th...@apache.org>
AuthorDate: Wed Nov 15 06:07:42 2017 -0800

    Capabilities Matrix: Stateful processing support in Apex Runner
---
 src/_data/capability-matrix.yml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/_data/capability-matrix.yml b/src/_data/capability-matrix.yml
index ff6d302..acac0ad 100644
--- a/src/_data/capability-matrix.yml
+++ b/src/_data/capability-matrix.yml
@@ -387,9 +387,9 @@ categories:
             l2: not implemented
             l3: Spark supports per-key state with <tt>mapWithState()</tt> so support should be straightforward.
           - class: apex
-            l1: 'No'
-            l2: not implemented
-            l3: Apex supports per-key state, so adding support for this should be easy.
+            l1: 'Partially'
+            l2: non-merging windows
+            l3: State is supported for non-merging windows. SetState and MapState are not yet supported.
           - class: gearpump
             l1: 'No'
             l2: not implemented

-- 
To stop receiving notification emails like this one, please contact
"commits@beam.apache.org" <co...@beam.apache.org>.