[
https://issues.apache.org/jira/browse/BEAM-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Burke updated BEAM-10976:
--------------------------------
Description:
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]
was:
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.
> Enable Bundle Finalization in Go SDK
> ------------------------------------
>
> Key: BEAM-10976
> URL: https://issues.apache.org/jira/browse/BEAM-10976
> Project: Beam
> Issue Type: New Feature
> Components: sdk-go
> Reporter: Robert Burke
> Priority: P2
>
> 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]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
