| H5A009 |
| SAS/ACCESS Interface to Google BigQuery 9.41 |
| Issue(s) Addressed: | Introduced: |
| 65552 | Running the SUMMARY procedure against a Google BigQuery table might return incorrect values for weight variables that have null values |
H5A001 |
| 65572 | The length of a string variable might be longer than specified with the MAX_CHAR_LEN= option |
H5A001 |
| 65573 | Reading in a BigQuery table might result in an error or slow performance |
H5A001 |
| 65884 | The ability to connect to a Google BigQuery database via proxy has been added to the SAS/ACCESS® Interface to Google BigQuery |
H5A001 |
| 65885 | The ability to connect to a Google BigQuery database via OAuth Authentication has been added to SAS/ACCESS® Interface to Google BigQuery |
H5A001 |
| 65886 | Trying to bulk load data into a Google BigQuery database might result in an error |
H5A001 |
| 65922 | Trying to read a Google BigQuery table that contains a variable defined as an array might result in a panic error and SAS® shutting down |
H5A002 |
| 66647 | Trying to subset a Google BigQuery table based on a Boolean variable might result in a performance issue |
H5A003 |
| 66712 | A generated list of BigQuery tables might be empty when the BigQuery dataset (schema) contains an underscore in its name |
H5A003 |
| 66996 | The ability to use BigQuery Storage API has been added to SAS/ACCESS® Interface to Google BigQuery |
H5A003 |
| 66997 | Improvements on the length of the STRING data type determination have been added to SAS/ACCESS® Interface to Google BigQuery |
H5A003 |
| 67127 | Materialized views are not included in the list of tables for Google BigQuery |
H5A003 |
| 67612 | Trying to access a Google BigQuery table might result in an error regarding column names not being unique |
H5A003 |
| 67616 | A library created in SAS® Studio for a Google BigQuery database might not display any tables |
H5A003 |
| 67618 | Trying to run the PRINT procedure against a Google BigQuery table might return the message "ERROR: CLI prepare error: Attribute cannot be set now" |
H5A003 |
| 67739 | The message "panic: runtime error" occurs if you do not include the SCHEMA= option in a LIBNAME statement when accessing a Google BigQuery database |
H5A003 |
| 66871 | Dates read in from a Google BigQuery database might show a difference from what is stored in the database |
H5A004 |
| 67015 | An incorrect format might be added to a column that is defined as a BOOLEAN or a NUMERIC data type in the Google BigQuery database |
H5A004 |
| 67420 | SAS/ACCESS® Interface to Google BigQuery changes the default data type used from TIMESTAMP to DATETIME while creating Google BigQuery tables |
H5A004 |
| 67421 | A query against Google BigQuery tables might result in the message "...Error: googleapi: Error 403: Response too large to return..." |
H5A005 |
| 67539 | SAS® might display an error when you attempt to delete a Google BigQuery view |
H5A005 |
| 67566 | The TRIM function might be included in a query that is passed to the BigQuery database |
H5A005 |
| 67567 | A query that includes the UNION of two queries that reference a Google BigQuery table might result in a performance issue and error |
H5A005 |
| 67707 | Unexpected characters might be appended to the end of a value on a string variable in a Google BigQuery table when it is read into SAS® software |
H5A005 |
| 67750 | Inserting data into a Google BigQuery table using the FEDSQL procedure might result in errors |
H5A005 |
| 67725 | An SQL procedure query that includes both inner and outer joins of Google BigQuery tables might result in a performance issue |
H5A007 |
| 67780 | Writing rows to Google BigQuery tables might result in the message "ERROR: During insert: String data, right-truncated..." |
H5A007 |
| 67983 | Using the DATASETS procedure to delete a Google BigQuery view might result in a "table or view not found" error |
H5A007 |
| 67974 | Poor performance occurs when data is read from Google BigQuery views with the OBS= data set option |
H5A007 |
| 68937 | Accessing a Google BigQuery database might result in "Error: googleapi: Error 429: per-user search quota temporarily exhausted..." |
H5A008 |
| 70583 | Reading a Google BigQuery table might take longer than normal and result in a crash or an “ERROR: During read: processStream retries exhausted” |
H5A009 |
| 70667 | The ability to turn on logging for the Go Layer was added to SAS/ACCESS® Interface to Google BigQuery |
H5A009 |
NOTE: If you install this hot fix, refer to KB0037934 for more information about the required GOMEMLIMIT environment variable.
NOTE: Refer to this Downloads page for the SAS/ACCESS to Google BigQuery Tools download.
NOTE: If you install this hot fix and have SAS Threaded Kernel DS2 and FedSQL Language Processors 9.41_M4 installed, you must also install hot fix E9Y008.
|
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes