[Feature] Support for BigQuery Emulator Endpoint in bigqueryio#34037
Closed
dvormagic wants to merge 1 commit intoapache:masterfrom
dvormagic:feature/bqio-emulator-endpoint
Closed
[Feature] Support for BigQuery Emulator Endpoint in bigqueryio#34037dvormagic wants to merge 1 commit intoapache:masterfrom dvormagic:feature/bqio-emulator-endpoint
dvormagic wants to merge 1 commit intoapache:masterfrom
dvormagic:feature/bqio-emulator-endpoint
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds support for connecting to a BigQuery emulator in the Apache Beam Go SDK by checking for the environment variable BIGQUERY_EMULATOR_HOST. When this variable is set, the BigQuery client is created using option.WithEndpoint(...) and option.WithoutAuthentication(), ensuring that writes and queries performed via bigqueryio.Write and bigqueryio.Query target the emulator rather than the production BigQuery service.
This change improves local development and testing scenarios by allowing Beam pipelines to interact with a BigQuery emulator seamlessly. It is backward-compatible with existing setups, as the default behavior remains unchanged if BIGQUERY_EMULATOR_HOST is not defined.