[ 
https://issues.apache.org/jira/browse/BEAM-11824?focusedWorklogId=553820&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-553820
 ]

ASF GitHub Bot logged work on BEAM-11824:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Feb/21 19:18
            Start Date: 17/Feb/21 19:18
    Worklog Time Spent: 10m 
      Work Description: y1chi commented on a change in pull request #14001:
URL: https://github.com/apache/beam/pull/14001#discussion_r577878578



##########
File path: 
runners/core-construction-java/src/main/java/org/apache/beam/runners/core/construction/WindowingStrategyTranslation.java
##########
@@ -295,10 +299,17 @@ public static FunctionSpec toProto(WindowFn<?, ?> 
windowFn, SdkComponents compon
             
.setAllowedLateness(windowingStrategy.getAllowedLateness().getMillis())
             
.setTrigger(TriggerTranslation.toProto(windowingStrategy.getTrigger()))
             .setWindowFn(windowFnSpec)
-            
.setAssignsToOneWindow(windowingStrategy.getWindowFn().assignsToOneWindow())
+            .setAssignsToOneWindow(windowFn.assignsToOneWindow())
+            .setMergeStatus(
+                windowFn instanceof InvalidWindows
+                    ? (((InvalidWindows) 
windowFn).getOriginalWindowFn().isNonMerging()

Review comment:
       probably stupid question: if the InvalidWindow only happens after GBK or 
combine, does the original window fn matter? should the MergeStatus always be 
ALREADY_MERGED for InvalidWindow? How should runner treat ALREADY_MERGED 
differently than NON_MERGING?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 553820)
    Time Spent: 1h  (was: 50m)

> WindowingStrategyTranslation does not set merge status in proto
> ---------------------------------------------------------------
>
>                 Key: BEAM-11824
>                 URL: https://issues.apache.org/jira/browse/BEAM-11824
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: P1
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> For example, session windows do not result in {{MergeStatus.NEEDS_MERGE}}. So 
> a runner that respects that bit (or doesn't special case sessions) will fail.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to