[jira] [Commented] (BEAM-184) Using Merging Windows and/or Triggers without a downstream aggregation should fail

["Kenneth Knowles (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903673#comment-15903673 ] 

Kenneth Knowles commented on BEAM-184:
--------------------------------------

I think with pipeline surgery in Java we are at a point where we can do this sort of validation effectively across runners. I will put it on the burn-down and choose an arbitrary owner, with the understanding that we have bigger priorities.

> 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
>             Fix For: First stable release
>
>
> 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.15#6346)