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

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

                Author: ASF GitHub Bot
            Created on: 21/Oct/19 08:32
            Start Date: 21/Oct/19 08:32
    Worklog Time Spent: 10m 
      Work Description: je-ik commented on issue #9841: [BEAM-8439] enable 
empty bundles in ParDoLifecycleTest
URL: https://github.com/apache/beam/pull/9841#issuecomment-544408386
 
 
   R: @mxm
   This could be the proper fix. But please validate my logic:
    - because `checkInvokeStartBundle` is called in 
`DoFnOperator.processWatermark1`, it is possible that `startBundle` gets 
invoked even though there are no actual elements flowing into the operator 
(e.g. higher parallelism than the actual number of elements). Therefore, the 
sequence of calls of the lifecycle methods is `startBundle` -> `finishBundle` 
with no intermediate `processElement`. It should be therefore captured in the 
test directly.
 
----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 331275)
    Time Spent: 0.5h  (was: 20m)

> Flink fails ParDoLifecycleTests
> -------------------------------
>
>                 Key: BEAM-8439
>                 URL: https://issues.apache.org/jira/browse/BEAM-8439
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>            Reporter: Jan Lukavský
>            Assignee: Jan Lukavský
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> ParDoLifecycleTest.testTeardownCalledAfterExceptionInFinishBundleStateful 
> fails consistently
>  



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

Reply via email to