Vertica ETL Data Source

VERTICA Channel supports Oracle, Postgres, MYSQL, MSSQL, DB2 connections.

You can configure and connect above mentioned DB-engines with JDBC. It allows you to extract the data from DB2 and other sources into your data pipeline in batches after configuring JDBC channel.

Prerequisite #

Upload an appropriate driver jar as per the RDBMS used in JDBC Data Source. Use the upload jar option.

For using DB2, create a DB2 Connection.

Schema Type #

See the topic Provide Schema for ETL Source → to know how schema details can be provided for data sources.

After providing schema type details, the next step is to configure the data source.

Configuring SQS - Vertica Data Source #

To add an SQS Vertica Data Source into your pipeline, drag the Data Source to the canvas and right-click on it to configure.

Connection Name #

Connections are the service identifiers. A connection name can be selected from the list if you have created and saved connection details for Vertica earlier. Or create one as explained in the topic - Vertica Connection →

Use the Test Connection option to ensure that the connection with the Amazon S3 channel is established successfully.

A success message states that the connection is available. In case of any error in test connection, edit the connection to resolve the issue before proceeding further.

Query #

Hive compatible SQL query to be executed in the component.

Metadata #

Enter the schema and select table. You can view the Metadata of the tables:

Table #

Select table of which you want to view Metadata.

Column Name #

Name of the column generated from the table.

Column Type #

Type of the column, for example: Text, Int

Nullable #

If the value of the column could be Nullable or not.

Add Configuration: Additional properties can be added using this option as key-value pairs.

Detect Schema #

Check the populated schema details. For more details, see Schema Preview →

Pre Action #

To understand how to provide SQL queries or Stored Procedures that will be executed during pipeline run, see Pre-Actions →.

Notes #

Optionally, enter notes in the Notes → tab and save the configuration.