You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Robert Bradshaw (JIRA)" <ji...@apache.org> on 2016/10/27 16:12:03 UTC
[jira] [Commented] (BEAM-184) Using Merging Windows and/or Triggers
without a downstream aggregation should fail
[ https://issues.apache.org/jira/browse/BEAM-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612368#comment-15612368 ]
Robert Bradshaw commented on BEAM-184:
--------------------------------------
This seems more like it should be a warning than an error, though it's forwards compatible to make it an error that can be relaxed later.
> Using Merging Windows and/or Triggers without a downstream aggregation should fail
> ----------------------------------------------------------------------------------
>
> Key: BEAM-184
> URL: https://issues.apache.org/jira/browse/BEAM-184
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Ben Chambers
> Priority: Minor
> Labels: backward-incompatible
>
> Both merging windows (such as sessions) and triggering only actually happen at an aggregation (GroupByKey). We should produce errors in any of these cases:
> 1. Merging window used without a downstream GroupByKey
> 2. Triggers used without a downstream GroupByKey
> 3. Window inspected after inserting a merging window and before the GroupByKey
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)