[
https://issues.apache.org/jira/browse/BEAM-10976?focusedWorklogId=744559&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-744559
]
ASF GitHub Bot logged work on BEAM-10976:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Mar/22 02:27
Start Date: 19/Mar/22 02:27
Worklog Time Spent: 10m
Work Description: lostluck commented on pull request #17045:
URL: https://github.com/apache/beam/pull/17045#issuecomment-1072921900
Daniel, Please do keep in mind We Should Not submit this with a manually
changed generate pb.go file. The bot tagged you in after my review for some
reason.
On Fri, Mar 18, 2022, 7:09 PM Daniel Oliveira ***@***.***>
wrote:
> ***@***.**** approved this pull request.
>
> This looks good to me, with one small nit that I don't think is worth
> blocking on. Let me know what you think of that suggestion and I can merge
> after.
> ------------------------------
>
> In sdks/go/pkg/beam/core/funcx/fn.go
> <https://github.com/apache/beam/pull/17045#discussion_r830423680>:
>
> > @@ -415,7 +432,7 @@ func SubReturns(list []ReturnParam, indices ...int)
[]ReturnParam {
> }
>
> // The order of present parameters and return values must be as follows:
> -// func(FnContext?, FnPane?, FnWindow?, FnEventTime?, FnType?,
FnRTracker?, (FnValue, SideInput*)?, FnEmit*) (RetEventTime?, RetOutput?,
RetError?)
> +// func(FnContext?, FnPane?, FnWindow?, FnEventTime?, FnType?,
FnRTracker?, FnBundleFinalization?, (FnValue, SideInput*)?, FnEmit*)
(RetEventTime?, RetOutput?, RetError?)
>
> Nit: Personally I think BundleFinalization should come before the
> RTracker, because the restriction is basically part of the main input so I
> feel it should come right before the main input. Not something I'd block
> on, just preference.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/beam/pull/17045#pullrequestreview-914956075>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/ADKDOFKXTQTJ7YXFCGYE4LDVAUZNNANCNFSM5QHNRCRA>
> .
> 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>.
>
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
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: 744559)
Time Spent: 10.5h (was: 10h 20m)
> Enable Bundle Finalization in Go SDK
> ------------------------------------
>
> Key: BEAM-10976
> URL: https://issues.apache.org/jira/browse/BEAM-10976
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-go
> Reporter: Robert Burke
> Assignee: Danny McCormick
> Priority: P3
> Time Spent: 10.5h
> Remaining Estimate: 0h
>
> Eg. to support acking pubsub/kafka messages as processed after the results
> have been properly committed by the runner.
> Note, that due to BEAM-10959 that when implementing this, an instruction must
> remain "active" until it's finalization occurs as well. Specifically, we
> should probably keep another map around for "to be finalized" process bundle
> instructions so we can return the appropriate "empty" response and not
> accidently evict them from the nearly equivalent inactive state until after
> finalization.
> [https://s.apache.org/beam-finalizing-bundles]
>
> (To be updated once [https://github.com/apache/beam/pull/13160] is merged and
> the programming guide updated with SDF content.)
> See also Java and Python approaches
> https://beam.apache.org/documentation/programming-guide/#bundle-finalization
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
