[ 
https://issues.apache.org/jira/browse/BEAM-14194?focusedWorklogId=749781&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-749781
 ]

ASF GitHub Bot logged work on BEAM-14194:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Mar/22 01:17
            Start Date: 30/Mar/22 01:17
    Worklog Time Spent: 10m 
      Work Description: youngoli opened a new pull request #17218:
URL: https://github.com/apache/beam/pull/17218


   SpannerIO.readChangeStream does not support autoscaling at the moment.
   In order to avoid customer confusion, we decided to throw an error if
   any algorithm is specified other than NONE.
   
   (cherry picked from commit a090e901b9a6335b2bdc82d62f8fb999d0010e3a)
   
   Cherry-pick of PR #17202 
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [x] [**Choose 
reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and 
mention them in a comment (`R: @username`).
    - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue, if applicable. This will automatically link the pull request to the 
issue.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [x] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/workflows/Build%20python%20source%20distribution%20and%20wheels/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/workflows/Python%20tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/workflows/Java%20Tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 749781)
    Time Spent: 1h 40m  (was: 1.5h)

> [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: 1h 40m
>  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)

Reply via email to