[GitHub] [beam] stephenmw opened a new issue, #24997: [Bug]: BigqueryIO: 404 on delete should be a success

[GitBox <gi...@apache.org>]

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

   ### What happened?
   
   BigqueryIO creates temporary datasets and tables and then later deletes them. Sometimes, the delete succeeds but the work-item commit fails. This means the temporary dataset/table is deleted but the work-item in which the delete happens is retried. Since BigqueryIO considers a 404 to be an error, the work-item is forever stuck when using a streaming job.
   
   This slows down draining of a job.
   
   To be resistant to failure, a 404 for a delete request should be treated as a success.
   
   ### Issue Priority
   
   Priority: 2 (default / most bugs should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [X] Component: IO connector
   - [ ] 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: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org