[
https://issues.apache.org/jira/browse/BEAM-14185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514378#comment-17514378
]
Daniel Oliveira commented on BEAM-14185:
----------------------------------------
I can fit this cherry-pick in since it's all ready and won't delay the release.
While it technically doesn't fit the requirements for a release-blocker (since
it isn't a "significant regression or loss of functionality"), it's in a weird
spot due to being a new feature. So sure, technically none of this can be a
regression since it's all a new feature of this release. But this is still a
known issue with noticeable user impact and the cherry-pick isn't delaying
anything, so I think it's worth getting in.
> [SpannerIO.readChangeStreams] Drop metadata tables at the end of the job
> ------------------------------------------------------------------------
>
> Key: BEAM-14185
> URL: https://issues.apache.org/jira/browse/BEAM-14185
> Project: Beam
> Issue Type: New Feature
> Components: io-java-gcp
> Affects Versions: 2.37.0
> Reporter: Thiago Nunes
> Assignee: Thiago Nunes
> Priority: P2
> Fix For: 2.38.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The SpannerIO.readChangeStreams Connector uses metadata tables to keep track
> of its internal state during execution. At the moment, these metadata tables
> linger after the execution, meaning that users will have to drop them
> manually.
> In this change, we would like to drop them automatically once the job
> finishes. This should only occur after all partitions have been processed
> successfully and marked as finished.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
