Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Vertica.md

JDBC Vertica Source Connector Read external data source data through JDBC. Spark<br/> Flink<br/> SeaTunnel Zeta<br/> You need to ensure that the has been placed in directory `${SEATUNNEL_HOME}/plugins/`. You need to ensure that the has been placed in directory `${SEATUNNEL_HOME}/lib/`. supports query SQL and can achieve projection effect. | Datasource | Supported versions | Driver | Url | Maven | ||-|-||-| | Vertica | Different dependency version has different driver class. | com.vertica.jdbc.Driver | jdbc:vertica://localhost:5433/vertica | | | Vertical Data Type | SeaTunnel Data Type | |--|--| | BIT | BOOLEAN | | TINYINT<br/>TINYINT UNSIGNED<br/>SMALLINT<br/>SMALLINT UNSIGNED<br/>MEDIUMINT<br/>MEDIUMINT UNSIGNED<br/>INT<br/>INTEGER<br/>YEAR | INT | | INT UNSIGNED<br/>INTEGER UNSIGNED<br/>BIGINT | LONG | | BIGINT UNSIGNED | DECIMAL(20,0) | | DECIMAL(x,y)(Get the designated column's specified column size.<38) | DECIMAL(x,y) | | DECIMAL(x,y)(Get the designated column's specified column size.>38) | DECIMAL(38,18) | | DECIMAL UNSIGNED | DECIMAL((Get the designated column's specified column size)+1,<br/>(Gets the designated column's number of digits to right of the decimal point.))) | | FLOAT<br/>FLOAT UNSIGNED | FLOAT | | DOUBLE<br/>DOUBLE UNSIGNED | DOUBLE | | CHAR<br/>VARCHAR<br/>TINYTEXT<br/>MEDIUMTEXT<br/>TEXT<br/>LONGTEXT<br/>JSON | STRING | | DATE | DATE | | TIME | TIME | | DATETIME<br/>TIMESTAMP | TIMESTAMP | | TINYBLOB<br/>MEDIUMBLOB<br/>BLOB<br/>LONGBLOB<br/>BINARY<br/>VARBINAR<br/>BIT(n) | BYTES | | GEOMETRY<br/>UNKNOWN | Not supported yet | | Name | Type | Required | Default | Description | |||-|--|-| | url | String | Yes | - | The URL of the JDBC connection. Refer to a case: jdbc:vertica://localhost:5433/vertica | | driver | String | Yes | - | The jdbc class name used to connect to the remote data source,<br/> if you use Vertica the value is `com.vertica.jdbc.Driver`. | | user | String | No | - | Connection instance user name | | password | String | No | - | Connection instance password | | query | String | Yes | - | Query statement | | connectionchecktimeout_sec | Int | No | 30 | The time in seconds to wait for the database operation used to validate the connection to complete | | partition_column | String | No | - | The column name for parallelism's partition, only support numeric type,Only support numeric type primary key, and only can config one column. | | partitionlowerbound | BigDecimal | No | - | The partition_column min value for scan, if not set SeaTunnel will query database get min

| | partitionupperbound | BigDecimal | No | - | The partition_column max value for scan, if not set SeaTunnel will query database get max value. | | partition_num | Int | No | job parallelism | The number of partition count, only support positive integer. default value is job parallelism | | fetch_size | Int | No | 0 | For queries that return a large number of objects,you can configure<br/> the row fetch size used in the query toimprove performance by<br/> reducing the number database hits required to satisfy the selection criteria.<br/> Zero means use jdbc default value. | | properties | Map | No | - | Additional connection configuration parameters,when properties and URL have the same parameters, the priority is determined by the <br/>specific implementation of the driver. For example, in MySQL, properties take precedence over the URL. | | common-options | | No | - | Source plugin common parameters, please refer to for details | If partitioncolumn is not set, it will run in single concurrency, and if partitioncolumn is set, it will be executed in parallel according to the concurrency of tasks. This example queries type_bin 'table' 16 data in your test "database" in single parallel and queries all of its fields. You can also specify which fields to query for final output to the console. ``` env { parallelism = 2 job.mode = "BATCH" } source{ Jdbc { url = "jdbc:vertica://localhost:5433/vertica" driver = "com.vertica.jdbc.Driver" connectionchecktimeout_sec = 100 user = "root" password = "123456" query = "select * from type_bin limit 16" } } transform { } sink { Console {} } ``` Read your query table in parallel with the shard field you configured and the shard data You can do this if you want to read the whole table ``` source { Jdbc { url = "jdbc:vertica://localhost:5433/vertica" driver = "com.vertica.jdbc.Driver" connectionchecktimeout_sec = 100 user = "root" password = "123456" query = "select * from type_bin" partition_column = "id" partition_num = 10 } } ``` It is more efficient to specify the data within the upper and lower bounds of the query It is more efficient to read your data source according to the upper and lower boundaries you configured ``` source { Jdbc { url = "jdbc:vertica://localhost:5433/vertica" driver = "com.vertica.jdbc.Driver" connectionchecktimeout_sec = 100 user = "root" password = "123456" query = "select * from type_bin" partition_column = "id" partitionlowerbound = 1 partitionupperbound = 500 partition_num = 10 } } ```