[iennae]

…a table while excluding specific columns

Problem:
The BigQuery documentation (https://cloud.google.com/bigquery/docs/search) needs a standalone, tested Python code sample demonstrating how to search a table while excluding specific columns (region tag bigquery_search_exclude_columns).

Solution:

• Add search_exclude_columns(project_id: str) -> None in bigquery/search/bigquery_search_exclude_columns.py (Search all columns of a BigQuery table except specified excluded columns using SELECT AS STRUCT * EXCEPT(...).)
• Add unit tests (bigquery/search/bigquery_search_exclude_columns_test.py) covering both the success path and API error handling (GoogleAPICallError)

Description

Fixes #

Checklist

Testing

• I have tested this change on a live environment and verified it works as intended.

Compliance & Style

• I have followed the Sample Guidelines.
• The README is updated with all relevant information (if applicable).
• If this PR adds a new sample directory: I updated the CODEOWNERS file.

---

Post-Approval Actions

• Please merge this PR for me once it is approved

[snippet-bot]

Here is the summary of changes.

You are about to add 1 region tag.

• bigquery/search/bigquery_search_exclude_columns.py:15, tag bigquery_search_exclude_columns

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[gemini-code-assist]

Code Review

This pull request introduces a new BigQuery search sample demonstrating how to search a table while excluding specific columns using SELECT AS STRUCT ... EXCEPT, along with its corresponding unit tests and configuration files. The feedback suggests updating the ignored Python versions in noxfile_config.py to align with the repository's testing guidelines of only testing the oldest and newest supported releases. Additionally, the unit tests should be improved by mocking the NotFound exception on query_job.result() rather than client.query() to more accurately simulate the asynchronous behavior of the BigQuery client.

[XrossFox]

So, i was taking a look at the comment by gemini, and i think it's correct: calling client.query() initially, doesn't return an exception right away, because it's an asynchronous method, that means the exception will be stored in the QueryObject.exception if it fails. According to the docs on QueryObject, calling QueryJob.result() blocks current execution and awaits for the operation to finish, then, if an exeption is encountered, the exception is raised, so a more accurate mock of exception handling would be to add the exception to the result of result().