Advanced SettingsCData Power BI Connector for Google BigQuery 2019 - Build 19.0.7354
The following sections detail connector settings that may be needed in advanced integrations.
Saving Result Sets
Large result sets must be saved in a temporary or permanent table. You can use the following properties to control table persistence:
Accessing Temporary Tables
You can use the following properties to manage temporary tables:
- AllowLargeResultSets: Store large result sets in temporary tables in a special dataset. If this is not set, an error is returned for result sets bigger than a certain size.
- TempTableDataset: Change the name of the dataset where temporary tables are saved.
- TempTableExpirationTime: Drop a temporary table the specified time after its creation.
Accessing Persistent Tables
Persist result sets larger than 128MB in a permanent table. To do so, you can set DestinationTable to the qualified name of the table. For example, "DestinationProjectId:DestinationDataSet.TableName". Subsequent queries replace the table with the new result set.
Set MaximumBillingTier to override your project limits on the maximum cost for any given query in a connection.
Registering Your Application
The OAuth user consent flow involves the authenticating user interacting with Google using the browser. To facilitate this, the connector is already registered as an OAuth application, but you may need to configure values specific to your application or organization. You may also want to display your own information instead of the CData app's when users log in to grant permissions.
- Log into the Google API Console.
- Click Create Project or select an existing project.
- Open the API Manager from the main menu and click Credentials -> Create Credentials -> OAuth Client Id.
If you are connecting from a desktop application, select Other.
If you are connecting from a Web application, select Web Application. In the Authorized Redirect URIs box, enter the URL you want to be used as a trusted redirect URL, where the user will return with the token that verifies that they have granted your app access.
- Click Create. The OAuthClientId and OAuthClientSecret are displayed.
- Click Library -> BigQuery API -> Enable API.
Customizing the SSL Configuration
By default, the connector attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats to do so.
Connecting Through a Firewall or Proxy
To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.
In addition, to authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
Set the following properties:
- To use a proxy-based firewall, set FirewallType, FirewallServer, and FirewallPort.
- To tunnel the connection, set FirewallType to TUNNEL.
- To authenticate, specify FirewallUser and FirewallPassword.
- To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.
Troubleshooting the Connection
To show connector activity from query execution to network traffic, use Logfile and Verbosity. The examples of common connection errors below show how to use these properties to get more context. Contact the support team for help tracing the source of an error or circumventing a performance issue.
- Authentication errors: Typically, recording a Logfile at Verbosity 4 is necessary to get full details on an authentication error.
- Queries time out: A server that takes too long to respond will exceed the connector's client-side timeout. Often, setting the Timeout property to a higher value will avoid a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 will show where the time is being spent.
- The certificate presented by the server cannot be validated: This error indicates that the connector cannot validate the server's certificate through the chain of trust. If you are using a self-signed certificate, there is only one certificate in the chain.
To resolve this error, you must verify yourself that the certificate can be trusted and specify to the connector that you trust the certificate. One way you can specify that you trust a certificate is to add the certificate to the trusted system store; another is to set SSLServerCert.