Add a new script to run BigQuery queries with python client #694
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| #!/bin/bash | ||
|
|
||
| bq mk --dataset test | ||
|
|
||
| bq query --use_legacy_sql=false < create.sql |
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,68 @@ | ||
| from google.cloud import bigquery | ||
| from google.cloud.bigquery.enums import JobCreationMode | ||
|
|
||
| import sys | ||
| from typing import TextIO, Any | ||
| from datetime import datetime | ||
|
|
||
| def log(*objects: Any, sep: str = ' ', end: str = '\n', file: TextIO = sys.stderr, severity: str = 'INFO') -> None: | ||
| """ | ||
| Mimics the built-in print() function signature but prepends a | ||
| timestamp and a configurable severity level to the output. | ||
|
|
||
| Args: | ||
| *objects: The objects to be printed (converted to strings). | ||
| sep (str): Separator inserted between values, default a space. | ||
| end (str): String appended after the last value, default a newline. | ||
| file (TextIO): Object with a write(string) method, default sys.stdout. | ||
| severity (str): The log level (e.g., "INFO", "WARNING", "ERROR"). | ||
| """ | ||
| # 1. Prepare the standard print content | ||
| # Use an f-string to join the objects with the specified separator | ||
| message = sep.join(str(obj) for obj in objects) | ||
|
|
||
| # 2. Prepare the log prefix | ||
| timestamp = datetime.now().strftime("%Y-%m-%d %H:%M:%S") | ||
| prefix = f"[{timestamp}] [{severity.upper()}]: " | ||
|
|
||
| # 3. Combine the prefix and the message | ||
| full_message = prefix + message | ||
|
|
||
| # 4. Use the file.write method to output the content | ||
| # The 'end' argument is handled explicitly here | ||
| file.write(full_message + end) | ||
|
|
||
| # Ensure the buffer is flushed (important for file/stream output) | ||
| if file is not sys.stdout and file is not sys.stderr: | ||
| file.flush() | ||
|
|
||
|
|
||
| job_config = bigquery.QueryJobConfig() | ||
| job_config.use_query_cache = False | ||
| client = bigquery.Client( | ||
| default_job_creation_mode=JobCreationMode.JOB_CREATION_OPTIONAL | ||
| ) | ||
|
|
||
| file = open('queries.sql', 'r') | ||
| TRIES = 3 | ||
| for query in file: | ||
| query = query.strip() | ||
| print("[", end='') | ||
| for i in range(TRIES): | ||
| log(f"\n[{i}]: {query}") | ||
| try: | ||
| client_start_time = datetime.now() | ||
| results = client.query_and_wait(query, job_config=job_config) | ||
| client_end_time = datetime.now() | ||
|
|
||
| client_time = client_end_time - client_start_time | ||
| client_time_secs = client_time.total_seconds() | ||
| endstr = "],\n" if i == 2 else "," | ||
| print(f"{client_time_secs}", end=endstr) | ||
|
|
||
| log(f"Job ID: **{results.job_id}**") | ||
| log(f"Query ID: **{results.query_id}**") | ||
| log(f"Client time: **{client_time}**") | ||
|
|
||
| except Exception as e: | ||
| log(f"Job failed with error: {e}", severity="ERROR") |
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I first tried to follow the steps with my company Google SSO and I failed in l. 16-18:
I don't think I can make our security team give the central
dataplane-developmentaccount permission to create GCP projects.I next tried with a fresh new Google account and failed in l. 6:
Whatever project name I provided, it always complained that
Requested entity already exists.I gave up at this point and will merge the PR without double-checking from our side. Thanks for contributing it anyways!