Starburst Netezza connector#
The Starburst Netezza connector allows querying and creating tables in an external IBM Netezza Database.
Requirements#
To connect to Netezza, you need:
Netezza version 11.2.0.0 or higher.
Network access from the coordinator and workers to the Netezza Server. Port 5480 is the default port.
Netezza JDBC driver, downloaded from IBM Fix Central.
A valid Starburst Enterprise license.
Configuration#
You need to add the JDBC driver, before creating catalogs:
Obtain the Netezza JDBC driver.
Add the JDBC JAR file to the SEP
plugin/netezza
directory on the coordinator and all workers.Restart SEP on every node.
Create a catalog properties file in etc/catalog
named, for example,
mynetezza.properties
to access the configured Netezza database in the
mynetezza
catalog. Configure the usage of the connector by specifying
the name netezza
and replace the connection properties as appropriate for
your setup.
connector.name=netezza
connection-url=jdbc:netezza://example.net:5480/database
connection-user=admin
connection-password=secret
More information about the supported JDBC URL format and parameters of the Netezza JDBC driver is available in the Netezza documentation.
Type mapping#
Because SEP and Netezza each support types that the other does not, this connector modifies some types when reading or writing data.
Netezza to SEP read type mapping#
The following read type mapping applies when data is read from existing tables in Netezza, or inserted into existing tables in Netezza from SEP.
Netezza type |
SEP type |
Notes |
---|---|---|
BOOLEAN, BOOL |
BOOLEAN |
|
BYTEINT, INT1 |
TINYINT |
|
SMALLINT, INT2 |
SMALLINT |
|
INTEGER, INT, INT4 |
INTEGER |
|
BIGINT, INT8 |
BIGINT |
|
DOUBLE PRECISION |
DOUBLE |
|
REAL, FLOAT(p) |
REAL |
Special values |
NUMERIC,(p, s), NUMERIC(p), NUMERIC, DECIMAL(p, s) |
DECIMAL(p, s) |
|
CHARACTER(n), CHAR(n), NCHAR(n) |
CHAR(n) |
|
CHARACTER VARYING(n), VARCHAR(n), NVARCHAR(n) |
VARCHAR(n) |
|
VARBINARY(n) |
VARBINARY |
ST_GEOMETRY(n) is not supported. |
DATE |
DATE |
|
TIME |
TIME(6) |
|
TIME WITH TIME ZONE |
TIME(6) WITH TIME ZONE |
|
TIMESTAMP |
TIMESTAMP(6) |
|
JSON, JSONB |
JSON |
No other types are supported.
SQL support#
The connector provides read and write access to data and metadata in the Netezza database. In addition to the globally available and read operation statements, the connector supports the following features:
SQL DELETE#
If a WHERE
clause is specified, the DELETE
operation only works if the
predicate in the clause can be fully pushed down to the data source.
SEP to Netezza write type mapping#
The following write type mapping applies when tables are created in Netezza from SEP.
SEP type |
Netezza type |
Notes |
---|---|---|
BOOLEAN |
BOOLEAN |
|
TINYINT |
BYTEINT |
|
SMALLINT |
SMALLINT |
|
INTEGER |
INTEGER |
|
BIGINT |
BIGINT |
|
REAL |
REAL |
|
DOUBLE |
DOUBLE PRECISION |
|
DECIMAL(p, s) |
DECIMAL(p, s) |
|
CHAR(n) |
NCHAR(n) |
max |
VARCHAR |
NVARCHAR(n) |
max |
VARBINARY |
VARBINARY(64000) |
|
DATE |
DATE |
|
TIME, TIME(p) |
TIME |
max supported precision is 6 |
TIME WITH TIME ZONE, TIME(p) WITH TIME ZONE |
TIME WITH TIME ZONE |
max supported precision is 6 |
TIMESTAMP, TIMESTAMP(p) |
TIMESTAMP |
max supported precision is 6, TIMESTAMP WITH TIME ZONE is not supported |
JSON |
JSONB |
No other type is supported.
General configuration properties#
The following properties can be used to configure how data types from the connected data source are mapped to Trino data types and how the metadata is cached in Trino.
Property name |
Description |
Default value |
---|---|---|
|
Configure how unsupported column data types are handled:
The respective catalog session property is |
|
|
Allow forced mapping of comma separated lists of data types to convert to
unbounded |
|
|
Support case insensitive database and collection names |
False |
|
1 minute |
|
|
Duration for which metadata, including table and column statistics, is cached |
0 (disabled caching) |
|
Cache the fact that metadata, including table and column statistics, is not available |
False |
Performance#
The connector includes a number of performance improvements, detailed in the following sections.
Table statistics#
The Netezza 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 Netezza and retrieved by the connector. Read more in Netezza documentation.
Pushdown#
The connector supports pushdown for a number of operations:
Aggregate pushdown for the following functions:
variance()
andvar_samp()
Dynamic filtering#
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 false
.
JDBC connection pooling#
You can improve performance by enabling JDBC connection pooling, which is disabled by default.