This document lists significant changes to the BigQuery Connector for SAP including version-specific enhancements.
To view all of the announcements from SAP on Google Cloud, see Release notes.
Updating BigQuery Connector for SAP
For information on how to update BigQuery Connector for SAP, see Update BigQuery Connector for SAP.
Version 2.8
Version 2.8 of the BigQuery Connector for SAP introduces the following enhancements:
Record compression option at field level: The BigQuery Connector for SAP offers record compression option at the field level. This option lets you replicate specified empty fields with their initial values to BigQuery, while still using record compression at the table level. For more information, see Record compression.
Transaction to view the version of BigQuery Connector for SAP: You can view the version of the BigQuery Connector for SAP installed on your system, by using the transaction
/GOOG/BQC_VERSION
.Enhanced HTTP error handling: The enhancement spot
/GOOG/ES_GCP_HTTP_CLIENT
lets you handle HTTP errors originating on the SAP client side, enabling more robust and customized integrations. For more information, see Enhanced HTTP error handling.Cluster table replication: An issue that prevented replication of multiple tables belonging to the same cluster within a single Mass Transfer ID has been resolved. From version 2.8 of the BigQuery Connector for SAP, you can replicate all cluster tables within a single Mass Transfer ID.
Version 2.7
Version 2.7 of the BigQuery Connector for SAP extends support for using the SAP SLT add-on - DMIS 2018 SP 11.
Version 2.6
Version 2.6 of the BigQuery Connector for SAP introduces the following enhancements:
Create Table tool: For empty source tables in SAP, the Create Table tool lets you create tables in the BigQuery dataset. For information about how to run the tool, see Create Table tool.
Mass Field Conversion tool: For mass conversion of target field mapping into
STRING
, you can use the Mass Field Conversion tool. For information about how to run the tool, see Mass Field Conversion tool.Read-only view of BigQuery Connector for SAP settings: For users who only need to view the BigQuery Connector for SAP settings, BigQuery Connector for SAP provides a custom transaction
/GOOG/SLT_SETT_DISP
. Administrators can grant access to this transaction for users who require read-only access only. For more information, see:- For workloads running on Google Cloud, see Create SAP roles and authorizations for viewing BigQuery Connector for SAP settings.
- For workloads running outside of Google Cloud, see Create SAP roles and authorizations for viewing BigQuery Connector for SAP settings.
Custom name for the PSE file: For the PSE file used for signing the JSON Key, which is used in JWT-based authentication, BigQuery Connector for SAP supports custom name. Previously, the PSE filename was required to be
SAPZG_JWT100.PSE
.The Break at First Error Flag (
BREAK
) is enabled by default: For new mass transfer keys created using the transaction/GOOG/SLT_SETTINGS
, theBREAK
flag is enabled by default.Enabled replication of cluster tables: BigQuery Connector for SAP supports replication of data from cluster tables to BigQuery. If you've applied a hotfix for the replication of data from cluster tables, then before updating the BigQuery Connector for SAP to version 2.6, you must delete the hotfix. For more information about deleting a hotfix, see the SAP page Creating, Editing, and Deleting Enhancement Implementations.
Enhancements to the replication validation report:
You can execute the replication validation report for specific tables in the mass transfer configuration. For more information, see:
- For workloads running on Google Cloud, see Run the Replication Validation tool.
- For workloads running outside of Google Cloud, see Run the Replication Validation tool.
All count fields of the table
/GOOG/REPL_RES
can accommodate values greater than the 32-bit integer limit (-2,147,483,648
to+2,147,583,647
).To follow the GoogleSQL lexical structure and syntax, all path expressions for querying counts on BigQuery are enclosed in backticks (`).
Fixed default audience for JWT based authentication: If you use Private Service Connect to connect to Google Cloud, then the default audience is correctly set during authentication. If you've applied a hotfix for this issue, then before updating the BigQuery Connector for SAP to version 2.6, you must delete the hotfix. For more information about deleting a hotfix, see the SAP page Creating, Editing, and Deleting Enhancement Implementations.
Fixed mapping of
INT8
data type: In supported versions of the SAP system, the mapping fromINT8
toINTEGER
data type functions as expected.Improved error messages: To help make troubleshooting easier, the clarity and comprehensibility of error messages are enhanced within the SDK.
Version 2.5
Enhancements
Support for RFC destinations: You can now use RFC destinations to connect to Google Cloud. To get you started, the transport files include sample RFC destinations. By using RFC destinations, you can perform the following: connect to Google Cloud through Private Service Connect endpoints, configure proxy server settings, and enable HTTP compression. For more information, see RFC destinations.
Support for using Private Service Connect: You can now use Private Service Connect (PSC) endpoints to allow private consumption of Google Cloud APIs and services. You specify your PSC endpoints in your RFC destinations that the connector uses to connect to Google Cloud. RFC destinations are new with version 2.5 of BigQuery Connector for SAP. For more information, see:
- For workloads running on Google Cloud, Specify Private Service Connector endpoints.
- For workloads running outside of Google Cloud, Specify Private Service Connector endpoints.
Token caching: To improve replication performance and fault tolerance, the BigQuery Connector for SAP now supports caching of the access token that allows access to BigQuery. For more information, see:
- For workloads running on Google Cloud, Enable token caching.
- For workloads running outside of Google Cloud, Enable token caching.
Automatic retry of access token retrieval for off-Google Cloud workloads: For SAP workloads that are running outside of Google Cloud, BigQuery Connector for SAP now automatically retries access token retrieval in case there is a failure to do so. You can control the number of retries by setting a value for the advanced setting parameter
CMD_EXEC_TRIES
. For more information, see Advanced settings.Authenticate to Google Cloud using JWT for off-Google Cloud workloads: For SAP workloads that are running outside of Google Cloud, you can now set up authentication to Google Cloud and authorization to access BigQuery using JSON Web Tokens (JWT) signed by Google Cloud. With JWT based authentication, you can authenticate to Google Cloud without the need of installing the Google Cloud CLI and creating an OS level command on the SAP LT Replication Server host. For more information, see Authentication using JWT to obtain access tokens.
Dynamic chunk sizing: The dynamic chunk size feature enables you to automatically reduce the chunk size and retry replication to BigQuery when the byte size of a chunk exceeds the maximum byte size for HTTP requests that BigQuery accepts. For more information, see Dynamic chunk size.
New enhancement exit: This version introduces a new enhancement exit that enables you to collect logging data in case of HTTP errors, after the HTTP calls to BigQuery API. You can use those logs for troubleshooting the HTTP errors. For more information, see Enhancement exits.
Load Simulation tool: The Load Simulation tool allows you to simulate load to BigQuery. This in turn enables you to assess replication performance, identify potential problems, understand the root cause of issues, and resolve them prior to actual replication of SAP data into BigQuery by using BigQuery Connector for SAP. For more information, see Load Simulation tool.
Version 2.2 to 2.4 (Not available)
Version 2.2 to 2.4 of BigQuery Connector for SAP are not available.
Version 2.1
Enhancements
Language support: The connector supports execution of background jobs that are running on the SAP LT Replication Server in all languages that SAP SLT supports. For more information, see Language support.
Troubleshooting invalid data errors: The connector contains improved error messages to help you troubleshoot invalid data errors. For more information, see Issue: Error messages related to invalid data.