[
https://issues.apache.org/jira/browse/BEAM-14194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514388#comment-17514388
]
Daniel Oliveira commented on BEAM-14194:
----------------------------------------
(I'm copy-pasting my comment from the other release-blocker because it is
completely applicable here)
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.readChangeStream] Throw error when autoscaling algorithm is not
> NONE
> -------------------------------------------------------------------------------
>
> Key: BEAM-14194
> URL: https://issues.apache.org/jira/browse/BEAM-14194
> Project: Beam
> Issue Type: New Feature
> Components: io-java-gcp, runner-dataflow
> Affects Versions: 2.37.0
> Reporter: Thiago Nunes
> Assignee: Thiago Nunes
> Priority: P2
> Fix For: 2.38.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> SpannerIO.readChangeStreams does not currently support the autoscaling
> feature. In order to avoid customer confusion, we decided to error out if an
> algorithm different than NONE is specified.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
