Problem Note 68937: Accessing a Google BigQuery database might result in "Error: googleapi: Error 429: per-user search quota temporarily exhausted..."
Accessing a Google BigQuery database might result in an error similar to the following:
ERROR: CLI error trying to establish connection: Error: googleapi: Error 429: per-user search quota temporarily exhausted
Details:
[
{
"@type": "type.googleapis.com/google.rpc.QuotaFailure",
"violations": [
{
"description": "per-user search quota temporarily exhausted",
"subject": "user"
}
]
}
]
,
rateLimitExceeded
ERROR: Error in the LIBNAME statement. retrieving query results, dump stack and retry 1 time>
To work around this limit, reduce the number of concurrent queries. If the error occurs, rerun the failing query when there are fewer queries being executed concurrently.
Click the Hot Fix tab in this note to access the hot fix for this issue.
With this hot fix, SAS has added an option to prevent a call to get the list of projects available to the user. The following table shows options that you can use in the LIBNAME statement:
LIBNAME Option Name |
Values |
Description |
PROJECT_LIST |
blank
list of projects separated by comma
|
The option can take an empty string (PROJECT_LIST="") to turn off the querying of the projects, in which case the PROJECT= project, the QUALIFIER= project (if present), and the Google BigQuery public data project (bigquery-public-data) are added to the list of available catalogs.
The user can also specify a list of other projects that they want access to by specifying those projects in the PROJECT_LIST=. For example, PROJECT=mainproj PROJECT_LIST="proj1,proj2,proj3"
The result is that all four projects (mainproj,proj1,proj2,proj3) as well as bigquery-public-data are in the available list of projects (for a total of five projects).
|
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Google BigQuery | Linux for x64 | 9.41 | | 9.4 TS1M6 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2022-04-20 13:24:24 |
Date Created: | 2022-02-21 16:54:24 |