kberezin-nshl opened a new issue, #32168: URL: https://github.com/apache/beam/issues/32168
### What happened? I think regular expressions that validate table spec (`BigQueryIO.TABLE_SPEC`) are too strict in terms of expecting 100% validity of GCP project name. When running our environment locally, we use very short names for GCP projects, like `abcd` (because it is both subproject folder name in our monorepo and GCP project name, so it's easier for us to set local env up), and that never caused any issues in any GCP-related software: all the emulators, Google-provided libraries, etc, - they just accept `abcd` and work. However, recently we started to use `BigQueryIO` connector in our dataflow jobs and suddenly, we encountered this issue with `BigQueryIO` that thinks that our `abcd:dataset.table` table specification is incorrect, with the error message being also super misleading. Clearly the format is correct, it's a project-validating part of the regex which didn't match. It's quite a big inconvenience for us to migrate to a longer project name for local dev, because of one library. I think GCP-related libraries should not behave differently and either this restriction should be enforced everywhere, or nowhere. And current state of things is that it is not enforced. ### 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 - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] 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-unsubscr...@beam.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
