[
https://issues.apache.org/jira/browse/BEAM-10976?focusedWorklogId=744554&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-744554
]
ASF GitHub Bot logged work on BEAM-10976:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Mar/22 02:09
Start Date: 19/Mar/22 02:09
Worklog Time Spent: 10m
Work Description: youngoli commented on a change in pull request #17045:
URL: https://github.com/apache/beam/pull/17045#discussion_r830423680
##########
File path: sdks/go/pkg/beam/core/funcx/fn.go
##########
@@ -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?)
Review comment:
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.
--
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: 744554)
Time Spent: 10h 20m (was: 10h 10m)
> 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: 10h 20m
> 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)
