New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need the new "unreachable" field to be supported by BigQuery::listDatasets API #3120
Comments
FYI, we're currently discussing how to approach this internally. |
Thanks @PhongChuong . Given we're getting an answer (and probably not a release) the earliest by Feb 12th, would it be possible for you to contact the BigQuery team and hold off this change while the community has time to adapt their software? The fact we're the only ones who submitted an issue shows a lot of lack of unawareness about the topic in general and certainly users won't upgrade timely and handle the new API results. |
Hi, |
@PhongChuong , sorry for the delay as I was on vacation. As stated by Google itself in the announcement sent to users:
Our use case - and most users, I guess - depends on this call being 100% reliable, i.e., either failing with an exception or returning all the datasets. Now an empty return in a region might mean "temporarily off" or no "datasets at all", which completely break the API. As suggested by Google itself:
We must fail the workflow given our use case - and I guess that's what most users want to do -, but currently there is no way to find out the empty response is due to an unreachable location and to do so. |
@sjmisterm, thanks for the context. |
Hi @PhongChuong , It's been a while since the last message. Is there an ETA already? |
Sorry for the delay. We're still trying to find staffing to work on this issue. I'll update as soon as we have a clear ETA. |
We are facing the same problem as issue googleapis/google-api-ruby-client#16987.
We need java API support for the new "unreachable" property in the
BigQuery::listDatasets
API response.This is urgent, as this change will take place starting on Feb 15th, as announced by Google.
The text was updated successfully, but these errors were encountered: