damondouglas opened a new issue, #28710:
URL: https://github.com/apache/beam/issues/28710

   ### What needs to happen?
   
   The output of this task are definitions and implementations of the Caller 
and SetupTeardown interfaces:
   
   ```java
   interface Caller<RequestT, ResponseT, ApiErrorT extends ApiException> 
extends Serializable {
       ResponseT call(RequestT request) throws ApiErrorT;
   }
   
   interface SetupTeardown<ErrorT extends Exception> extends Serializable {
        void setup() extends ErrorT;
        void teardown() extends ErrorT;
   }
   ```
   
   Test implementations of `Caller` and `SetupTeardown` call the quota aware 
endpoint built and deployed from #28708 and #28709. Additionally, configurable 
mock implementations mimic response and error scenarios to supporting unit 
testing.
   
   # Measures of Ready
   
   Work on this task depends on:
   - #28708
   - #28709
   
   # Measures of Done
   
   This task is considered done when:
   
   - [ ] Caller and SetupTeardown interfaces exist in the RRIO project
   - [ ] Test implementations successfully call the deployed mock quota aware 
endpoint
   - [ ] Mock implementations successfully mimic error and response cases
   
   
   ### Issue Priority
   
   Priority: 2 (default / most normal work should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
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]

Reply via email to