Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Need to support dataset.list and jobs.list API new field feature

Open
#16,987 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
google-cloud, ruby
Domain
api, cloud

Research direction

Start by locating the generated BigQuery definitions for the datasets.list and jobs.list APIs and inspect their response representations. Confirm how new response fields are exposed in the Ruby client, then verify that both APIs include the unreachable field and run the repository's relevant tests or generation checks if available.

Written by the indexing model from the issue text.

Description

Hello,

I have received the following email from Google:

Hello Google BigQuery Customer,

We are writing to let you know that a new field will be added to the response of the datasets.list API and jobs.list API calls in BigQuery starting February 15, 2024.

What do you need to know?
Currently, in the rare event that one or more GCP regions become unreachable for a prolonged period, datasets.list and jobs.list API calls will fail if the response should include data from the unreachable region.

Starting February 15, 2024, these calls will succeed, but with the additional field `unreachable` included to indicate the locations where data might have been omitted from the datasets.list and jobs.list responses due to the prolonged unreachability of the entire region or multi-region.

Under normal circumstances, this field will be empty. However, if you depend on retrieving a complete list of all your datasets and jobs from the datasets.list and jobs.list APIs, you should start considering the values of this new field when present.

What do I need to do?
We recommend the following steps to make the most of the new field provided in the output:

1. Review the regions from which you are making datasets.list and jobs.list API calls.
2. After February 15, 2024, review the new "unreachable" field in the datasets.list and jobs.list API responses.
3. Examine the contents of this field to identify any unreachable locations. If your API integration with BigQuery relies on obtaining a full list of datasets/jobs from all regions/multi-regions where relevant data exists, you may need to adjust your integration based on specific scenarios.
4. Depending on the situation, you may choose to fail the workflow, issue a warning, or continue without warning if the `unreachable` field is populated.

These recommended actions will help you ensure that you are receiving a complete list of datasets from all regions.

Thank you for choosing Google Big Query.

It appears that a new unreachable field will be added to the jobs.list and datasets.list APIs. This change will modify the interfaces of these two APIs. When can I expect this SDK to be updated to reflect this change?

Dominant language
Ruby
Stars
2.9k
Forks
888
Avg merge
8m
Merged PRs (30d)
241

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-api-ruby-client

All issues in googleapis/google-api-ruby-client

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.