acf0d91ebd
Co-authored-by: Satish Chinthanippu <satishchinthanippu@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
98 lines
5.2 KiB
Markdown
98 lines
5.2 KiB
Markdown
# Teradata
|
|
|
|
This page guides you through the process of setting up the Teradata destination connector.
|
|
|
|
## Prerequisites
|
|
|
|
To use the Teradata destination connector, you'll need:
|
|
|
|
- Access to a Teradata Vantage instance
|
|
|
|
**Note:** If you need a new instance of Vantage, you can install a free version called Vantage Express in the cloud on [Google Cloud](https://quickstarts.teradata.com/vantage.express.gcp.html), [Azure](https://quickstarts.teradata.com/run-vantage-express-on-microsoft-azure.html), and [AWS](https://quickstarts.teradata.com/run-vantage-express-on-aws.html). You can also run Vantage Express on your local machine using [VMware](https://quickstarts.teradata.com/getting.started.vmware.html), [VirtualBox](https://quickstarts.teradata.com/getting.started.vbox.html), or [UTM](https://quickstarts.teradata.com/getting.started.utm.html).
|
|
|
|
You'll need the following information to configure the Teradata destination:
|
|
|
|
- **Host** - The host name of the Teradata Vantage instance.
|
|
- **Username**
|
|
- **Password**
|
|
- **Default Schema Name** - Specify the schema (or several schemas separated by commas) to be set in the search-path. These schemas will be used to resolve unqualified object names used in statements executed over this connection.
|
|
- **JDBC URL Params** (optional)
|
|
|
|
[Refer to this guide for more details](https://downloads.teradata.com/doc/connectivity/jdbc/reference/current/jdbcug_chapter_2.html#BGBHDDGB)
|
|
|
|
## Sync overview
|
|
|
|
### Output schema
|
|
|
|
Each stream will be output into its own table in Teradata. Each table will contain 3 columns:
|
|
|
|
- `_airbyte_ab_id`: a unique uuid assigned by Airbyte to each event that is processed. This is the primary index column. The column type in Teradata is `VARCHAR(256)`.
|
|
- `_airbyte_emitted_at`: a timestamp representing when the event was pulled from the data source. The column type in Teradata is `TIMESTAMP(6)`.
|
|
- `_airbyte_data`: a json blob representing with the event data. The column type in Teradata is `JSON`.
|
|
|
|
### Features
|
|
|
|
The Teradata destination connector supports the
|
|
following[ sync modes](https://docs.airbyte.com/cloud/core-concepts#connection-sync-modes):
|
|
|
|
| Feature | Supported?\(Yes/No\) | Notes |
|
|
| :----------------------------- | :------------------- | :---- |
|
|
| Full Refresh Sync | Yes | |
|
|
| Incremental - Append Sync | Yes | |
|
|
| Incremental - Append + Deduped | No | |
|
|
| Namespaces | Yes | |
|
|
|
|
### Performance considerations
|
|
|
|
## Getting started
|
|
|
|
### Requirements
|
|
|
|
You need a Teradata user with the following permissions:
|
|
|
|
- can create tables and write permission.
|
|
- can create schemas e.g:
|
|
|
|
You can create such a user by running:
|
|
|
|
```
|
|
CREATE USER airbyte_user as perm=10e6, PASSWORD=<password>;
|
|
GRANT ALL on dbc to airbyte_user;
|
|
|
|
```
|
|
|
|
You can also use a pre-existing user but we highly recommend creating a dedicated user for Airbyte.
|
|
|
|
### Setup guide
|
|
|
|
#### Set up the Teradata Destination connector
|
|
|
|
1. Log into your Airbyte Open Source account.
|
|
2. Click **Destinations** and then click **+ New destination**.
|
|
3. On the Set up the destination page, select **Teradata** from the **Destination type** dropdown.
|
|
4. Enter the **Name** for the Teradata connector.
|
|
5. For **Host**, enter the host domain of the Teradata instance
|
|
6. For **Default Schema**, enter the Default Schema name. The default value is public.
|
|
7. For **User** and **Password**, enter the database username and password.
|
|
8. To customize the JDBC connection beyond common options, specify additional supported [JDBC URL parameters](https://downloads.teradata.com/doc/connectivity/jdbc/reference/current/jdbcug_chapter_2.html#BGBHDDGB) as key-value pairs separated by the symbol & in the **JDBC URL Params** field.
|
|
|
|
Example: key1=value1&key2=value2&key3=value3
|
|
|
|
These parameters will be added at the end of the JDBC URL that the AirByte will use to connect to your Teradata database.
|
|
|
|
## Changelog
|
|
|
|
<details>
|
|
<summary>Expand to review</summary>
|
|
|
|
| Version | Date | Pull Request | Subject |
|
|
| :------ | :--------- | :---------------------------------------------- | :------------------------------------------------------- |
|
|
| 0.1.6 | 2024-06-24 | https://github.com/airbytehq/airbyte/pull/39455 | Fix for Parameter 2 length size |
|
|
| 0.1.5 | 2024-01-12 | https://github.com/airbytehq/airbyte/pull/33872 | Added Primary Index on \_airbyte_ab_id to fix NoPI issue |
|
|
| 0.1.4 | 2023-12-04 | https://github.com/airbytehq/airbyte/pull/28667 | Make connector available on Airbyte Cloud |
|
|
| 0.1.3 | 2023-08-17 | https://github.com/airbytehq/airbyte/pull/30740 | Enable custom DBT transformation |
|
|
| 0.1.2 | 2023-08-09 | https://github.com/airbytehq/airbyte/pull/29174 | Small internal refactor |
|
|
| 0.1.1 | 2023-03-03 | https://github.com/airbytehq/airbyte/pull/21760 | Added SSL support |
|
|
| 0.1.0 | 2022-12-13 | https://github.com/airbytehq/airbyte/pull/20428 | New Destination Teradata Vantage |
|
|
|
|
</details> |