tomlynchRNA opened a new issue, #25225: URL: https://github.com/apache/beam/issues/25225
### What would you like to happen? Hello, I am running an Apache Beam pipeline and streaming inserts into Google BigQuery with the Python SDK. I am facing an issue where because Beam only creates tables once before storing the name a list called `_KNOWN_TABLES`, if the table is deleted while the pipeline is running after Beam having already created it, further inserts will error out with a 404 and not attempt to re-create it. You can see here where the `_create_table_if_needed` method returns early if the table is already in `_KNOWN_TABLES`: https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/gcp/bigquery.py#L1463 I have the pipeline create disposition set to the default CREATE_IF_NEEDED, therefore I expect that if the table does not exist (and **is needed**) to stream inserts, that it will be created. I propose that a mechanism be implemented allowing this behaviour, and would be willing to make the changes & open a pull request. Looking forward to your thoughts, Tom ### Issue Priority Priority: 2 (default / most feature requests should be filed as P2) ### Issue Components - [X] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
