Onboarding Data from Netezza
Creating a Netezza Source
For onboarding data from a Netezza source, see Onboarding a RDBMS Source. Ensure that the Source Type selected is Netezza.
- Ensure that you manually download the Netezza JDBC driver from the IBM portal.
- Create
lib/dist-jobsdirectory under the$IW_HOME/lib/ingestion/connectors/netezzafolder, so that the directory structure becomes$IW_HOME/lib/ingestion/connectors/netezza/lib/dist-jobs, and place the downloaded driver inside it.
To upload driver jars for Kubernetes-based Installation:
Step 1: Create a structured directory in your local or VM bastion.
mkdir -p lib/ingestion/connectors/<connector_name>/<path>/<jars>
connector_name with the respective connectors, path and keep the jars in the source directory.
Step 2: Get the list of the pods and select the ingestion pod.
kubectl get pods -n <namespace>
Step 3: Copy the jars to the ingestion pod.
kubectl cp lib
release-531-ingestion-665854b7b-2jn5q:/opt/infoworks/uploads/ -c ingestion -n <namespace_name>
Step 4: Delete the ingestion pod.
kubectl delete pods release-531-ingestion-665854b7b-2jn5q -n <namespace_name>
Step 5: Wait for the pod's state to change to the running state your changes are in.
Netezza Configurations
| Field | Description |
|---|---|
| Fetch Data Using | The mechanism through which Infoworks fetches data from the database. |
| Connection URL | The connection URL through which Infoworks connects to the database. The URL must be in the following format: jdbc:netezza://<ip>:<port>/<databasename> |
| Username | The username for the connection to the database. |
| Authentication Type for Password | Select the authentication type from the dropdown. For example, Infoworks Managed or External Secret Store. If you select Infoworks Managed, then provide Authentication Password for Password. If you select External Secret Store, then select the Secret which contains the password. |
| Source Schema | The schema in the database to be crawled. The schema value is case sensitive. |
| Custom Tags | This dropdown provides the list of tags which you can choose. It can be used to identify/segregate the source based on the selected tags. |
Once the settings are saved, you can test the connection.
Configuring a Netezza Table
With the source metadata in the catalog, you can now configure the table for CDC and incremental synchronization.
- Click the Configuration link, for the desired table.
- Provide the ingestion configuration details.
| Field | Description |
|---|---|
| Query | The custom query based on which the table has been created. |
| Ingest Type | The type of synchronization for the table. The options include full refresh and incremental. |
| Natural Keys | The combination of keys to uniquely identify the row. This field is mandatory in incremental ingestion tables. It helps in identifying and merging incremental data with the already existing data on target. |
| Incremental Mode | The option to indicate if the incremental data must be appended or merged to the base table. This field is displayed only for incremental ingestion. The options include append, merge and insert overwrite. |
| Incremental Fetch Mechanism | The fetch mechanism options include Archive Log and Watermark Column. This field is available only for Oracle log-based ingestion. |
| Watermark Column | Select single/multiple watermark columns to identify the incremental records. The selected watermark column(s) should be of the same datatype. |
| Enable Watermark Offset | For Timestamp and Date watermark columns, this option enables an additional offset (decrement) to the starting point for ingested data. Records created or modified within the offset time period are included in the next incremental ingestion job. |
| Ingest subset of data | The option to configure filter conditions to ingest a subset of data. This option is available for all the RDBMS and Generic JDBC sources. For more details, see Filter Query for RDBMS Sources |
| Sorting Columns | Select columns on which the target table will be sorted. |
Target Configuration
Configure the following fields:
| Field | Description |
|---|---|
| Target Table Name | The name of the target table. |
| Catalog Name | The name of the target catalog. |
| Staging Catalog Name | The staging catalog name for temp tables. |
| Staging Schema Name | The staging schema name for temp tables. |
| Storage Format | The format in which the tables must be stored. The options include Read Optimized (Delta), Read Optimized (Parquet), Read Optimized (ORC), Write Optimized (Avro), Universal Format (UniForm) and Delimited text files. |
| Partition Column | The column used to partition the data in target. Selecting the Create Derived Column option allows you to derive a column and then use that as the partition column. This option is enabled only if the partition column datatype is date or timestamp. Provide the Derived Column Function and Derived Column Name. Data will be partitioned based on this derived column. |
Optimization Configuration
Configure the following fields:
| Field | Description |
|---|---|
| Split By Column | The column used to crawl the table in parallel with multiple connections to database. Split-by column can be an existing column in the data. Any column for which minimum and maximum values can be computed, can be a split-by key. Select the Create Derived Split Column option and provide the Derived Split Column Function to derive a column from the Split By column. This option is enabled only if the Split By column datatype is date or timestamp. The data will be split based on the derived value. |
| Is Wide Table | The option to be enabled when any insert, update or delete statement in logs can exceed 4000 characters. |
Advanced Configurations
Following are the steps to set advanced configuration for a table:
- Click the Data Catalog menu and click Ingest for the required source.
- Click the Configure Tables tab, click the Advanced Configuration tab and click Add Configuration.
- Enter key, value, and description. You can also select the configuration from the list displayed.
Sync Data to Target
Using this option, you can configure the Target connections and sync data as described in the section Synchronizing Data to External Target
The following are the steps to sync data to target.
- From the Data Sources menu, select one of the tables and click View Source/Ingest button.
- Select the source table to be synchronized to Target.
- Click the Sync Data to Target button.
- Enter the mandatory fields as listed in the table below:
| Field | Description |
|---|---|
| Job Name | The name of the ingestion job. |
| Max Parallel Tables | The maximum number of tables that can be crawled at a given instance. |
| Compute Cluster | The template based on which the cluster will spin up for each table.The compute clusters created by admin and are accessible by the user are listed in the drop down. |
| Overwrite Worker Count | The option to override the maximum and minimum number of worker node values as configured in the compute template |
| Number of Worker Nodes | The number of worker nodes that will spin up in the cluster. |
| Save as a Table Group | The option to save the list of tables as a table group. |
Click Onboarding a RDBMS Source to navigate back to complete the onboarding process.