[
https://issues.apache.org/jira/browse/BEAM-7913?focusedWorklogId=666175&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-666175
]
ASF GitHub Bot logged work on BEAM-7913:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Oct/21 08:26
Start Date: 18/Oct/21 08:26
Worklog Time Spent: 10m
Work Description: scwhittle commented on pull request #15531:
URL: https://github.com/apache/beam/pull/15531#issuecomment-945508673
This can be useful in integration tests to drain after input has been
consumed (determined for example by viewing source progress such as pubsub
oldest unacked)
On Fri, Oct 15, 2021 at 6:34 PM reuvenlax ***@***.***> wrote:
> what's the use case?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/beam/pull/15531#issuecomment-944438537>, or
> unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/ABBZZTGX33U7C23PIRPFEATUHBJXVANCNFSM5EH7KA5A>
> .
> Triage notifications on the go with GitHub Mobile for iOS
>
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
>
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 666175)
Time Spent: 0.5h (was: 20m)
> Add drain() to DataflowPipelineJob
> ----------------------------------
>
> Key: BEAM-7913
> URL: https://issues.apache.org/jira/browse/BEAM-7913
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Sam Whittle
> Priority: P3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Dataflow supports draining jobs but there is no easy programatic way to do it.
> I propose adding a drain() method to DataflowPipelineJob similar to the
> existing cancel() method (inherited from PipelineResult).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
