You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Robert Burke (Jira)" <ji...@apache.org> on 2022/02/23 18:18:00 UTC

[jira] [Commented] (BEAM-10976) Enable Bundle Finalization in Go SDK

    [ https://issues.apache.org/jira/browse/BEAM-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496973#comment-17496973 ] 

Robert Burke commented on BEAM-10976:
-------------------------------------

Just to be clear, there should be a design doc for this, since it affects the user surface. We need to represent the user experience of adding a finalizer and why this option vs other alternatives.

> 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
>
> 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)