beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mergebot-r...@apache.org
Subject [beam-site] 01/02: Update Mapreduce capability matrix when/how entries
Date Fri, 22 Sep 2017 18:43:49 GMT
This is an automated email from the ASF dual-hosted git repository.

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

commit d9e10e65880ffb3b936cfe38e6d75d3f940e1f34
Author: melissa <melissapa@google.com>
AuthorDate: Thu Sep 21 09:41:58 2017 -0700

    Update Mapreduce capability matrix when/how entries
---
 src/_data/capability-matrix.yml | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/src/_data/capability-matrix.yml b/src/_data/capability-matrix.yml
index 1c1171d..b0ea35a 100644
--- a/src/_data/capability-matrix.yml
+++ b/src/_data/capability-matrix.yml
@@ -577,7 +577,7 @@ categories:
             l3: ''
           - class: mapreduce
             l1: 'No'
-            l2: It is a batch-only runner, and intermediate trigger firings are effectively
meaningless.
+            l2: batch-only runner
             l3: ''
 
       - name: Event-time triggers
@@ -608,7 +608,7 @@ categories:
             l3: ''
           - class: mapreduce
             l1: 'No'
-            l2: Currently watermark progress jumps from the beginning of time to the end
of time once the input has been fully consumed, thus no additional triggering granularity
is available.
+            l2: ''
             l3: ''
 
       - name: Processing-time triggers
@@ -639,7 +639,7 @@ categories:
             l3: ''
           - class: mapreduce
             l1: 'No'
-            l2: From the perspective of triggers, processing time currently jumps from the
beginning of time to the end of time once the input has been fully consumed, thus no additional
triggering granularity is available.
+            l2: ''
             l3: ''
 
       - name: Count triggers
@@ -670,7 +670,7 @@ categories:
             l3: ''
           - class: mapreduce
             l1: 'No'
-            l2: Elements are processed in the largest bundles possible, so count-based triggers
are effectively meaningless.
+            l2: ''
             l3: ''
 
       - name: '[Meta]data driven triggers'
@@ -702,7 +702,7 @@ categories:
             l3:
           - class: mapreduce
             l1: 'No'
-            l2: pending model support
+            l2: ''
             l3:
 
       - name: Composite triggers
@@ -732,8 +732,8 @@ categories:
             l2: ''
             l3: ''
           - class: mapreduce
-            l1: 'Yes'
-            l2: fully supported
+            l1: 'No'
+            l2: ''
             l3: ''
 
       - name: Allowed lateness
@@ -764,7 +764,7 @@ categories:
             l3: ''
           - class: mapreduce
             l1: 'No'
-            l2: No data is ever late.
+            l2: ''
             l3: ''
 
       - name: Timers
@@ -794,8 +794,8 @@ categories:
             l2: not implemented
             l3: ''
           - class: mapreduce
-            l1: 'Partially'
-            l2: not implemented
+            l1: 'No'
+            l2: ''
             l3: ''
 
   - description: How do refinements relate?
@@ -833,8 +833,8 @@ categories:
             l2: fully supported
             l3: ''
           - class: mapreduce
-            l1: 'Yes'
-            l2: fully supported
+            l1: 'No'
+            l2: batch-only runner
             l3: ''
 
       - name: Accumulating
@@ -864,8 +864,8 @@ categories:
             l2: ''
             l3: ''
           - class: mapreduce
-            l1: 'Yes'
-            l2: fully supported
+            l1: 'No'
+            l2: ''
             l3: ''
 
       - name: 'Accumulating &amp; Retracting'
@@ -897,5 +897,5 @@ categories:
             l3: ''
           - class: mapreduce
             l1: 'No'
-            l2: pending model support
+            l2: ''
             l3: ''

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

Mime
View raw message