[
https://issues.apache.org/jira/browse/BEAM-14313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525904#comment-17525904
]
Kenneth Knowles commented on BEAM-14313:
----------------------------------------
I believe this is intended behavior, in a sense. The finalize is an optional
step. Not all streaming systems have a serializable checkpoint mark - for
example those where the server side tracks how much has been consumed. So when
it is serialized and then deserialized it will be null. But if it is held in
memory it can be finalized. I think it is worth revisiting this and documenting
it, at P2 though.
And please do provide the information that Kyle has requested.
> [IT Tests] Message not acknowledged using Direct Runner
> -------------------------------------------------------
>
> Key: BEAM-14313
> URL: https://issues.apache.org/jira/browse/BEAM-14313
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp, runner-direct
> Affects Versions: 2.36.0
> Reporter: Amrane AIT ZEOUAY
> Priority: P1
> Labels: GCP, test, test-stability
> Attachments: JmsCheckpointMark.java.png,
> UnboundedReadEvaluatorFactory.java.png
>
>
> When running integration tests using direct runner, the messages are not
> acknowledged. The function *finalizeCheckpoint()* is not called because the
> shard's checkpoint is always null.
> !UnboundedReadEvaluatorFactory.java.png!
> The acknowledgement is called inside of the function *finalizeCheckpoint()*
> !JmsCheckpointMark.java.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
