Starburst Oracle connector#
The Starburst Oracle connector is an extended version of the Oracle Connector, the initial configuration and usage is identical.
The additional features of the connector require a valid Starburst Enterprise license, unless otherwise noted.
The following improvements are included:
The connector includes a number of performance improvements, detailed in the following sections.
The connector is able to read data from Oracle using multiple parallel connections.
Determines the parallelism method. Possible values are:
Maximum number of parallel connections for a table scan
This feature is available for free, and does not require a valid license.
The Oracle connector supports table and column statistics to improve query processing performance based on the actual data in the data source.
The statistics are collected by Oracle and retrieved by the connector.
To collect statistics for a table, add the following statement to your Oracle database:
EXECUTE DBMS_STATS.GATHER_TABLE_STATS('USER_NAME', 'TABLE_NAME');
See Oracle’s documentation for additional options and instructions on invoking a procedure when you’re not using SQL*Plus.
The connector supports pushdown for the following aggregate functions:
Additionally, for the aggregate functions below, pushdown is only supported
DOUBLE type columns:
Dynamic filtering is enabled by default. It causes the connector to wait for dynamic filtering to complete before starting a JDBC query.
You can disable dynamic filtering by setting the property
dynamic-filtering.enabled in your catalog properties file to
Caching table projections#
The connectors supports table scan redirection to improve performance and reduce load on the data source.
The connector includes a number of security-related features, detailed in the following sections.
Oracle connector supports user impersonation. In the Oracle connector, user impersonation creates proxy user accounts and authorizes users to connect through them in Oracle database.
Enable user impersonation in the catalog file:
For more information, go to docs.oracle.com.
The Oracle connector supports Kerberos-based authentication with the following configuration:
oracle.authentication.type=KERBEROS email@example.com kerberos.client.keytab=etc/kerberos/example.keytab kerberos.config=etc/kerberos/krb5.conf
In this configuration the user
firstname.lastname@example.org, as defined in the
principal property, connects to the database. The related Kerberos
service ticket is located in the
Kerberos credential pass-through#
You can configure the Starburst Oracle connector to pass through Kerberos credentials, received by SEP, to the Oracle database. To configure Kerberos and SEP, see Kerberos credential pass-through.
After you configure Kerberos and SEP, edit the properties file to enable the connector to pass the credentials from the server to the database.
Confirm the correct Kerberos client configuration properties in the catalog properties file. For example:
oracle.authentication.type=KERBEROS_PASS_THROUGH http.authentication.krb5.config=/etc/krb5.conf http-server.authentication.krb5.service-name=exampleServiceName http-server.authentication.krb5.keytab=/path/to/Keytab/File
Now any database accessed using SEP is subject to the Kerberos defined data access restrictions and permissions.
Password credential pass-through#
The connector supports password credential pass-through. This means that the data SEP accesses is the same as the data available to a user who has direct access to the data source.
To enable it, edit the catalog properties file to include the authentication type:
For more information about configurations and limitations, see Password credential pass-through.