Skip to main content

Exasol [ARCHIVED]

Exasol is the in-memory database built for analytics.

Sync overview​

Output schema​

Each Airbyte Stream becomes an Exasol table and each Airbyte Field becomes an Exasol column. Each Exasol table created by Airbyte will contain 3 columns:

  • _AIRBYTE_AB_ID: a uuid assigned by Airbyte to each event that is processed. The column type in Exasol is VARCHAR(64).
  • _AIRBYTE_DATA: a json blob representing with the event data. The column type in Exasol is VARCHAR(2000000).
  • _AIRBYTE_EMITTED_AT: a timestamp representing when the event was pulled from the data source. The column type in Exasol is TIMESTAMP.

Features​

The Exasol destination supports the following features:

FeatureSupported? (Yes/No)Notes
Full Refresh SyncYes
Incremental - Append SyncYes
Incremental - Append + DedupedNo
NormalizationNo
NamespacesYes
SSL connectionYesTLS
SSH Tunnel SupportNo

Limitations​

Maximum data size two million characters​

Exasol does not have a special data type for storing data of arbitrary length or JSON. That's why this connector uses type VARCHAR(2000000) for storing Airbyte data.

Getting started​

Requirements​

To use the Exasol destination, you'll need Exasol database version 7.1 or above.

Network Access​

Make sure your Exasol database can be accessed by Airbyte. If your database is within a VPC, you may need to allow access from the IP you're using to expose Airbyte.

Permissions​

As Airbyte namespaces allow to store data into different schemas, there are different scenarios requiring different permissions assigned to the user account. The following table describes 4 scenarios regarding the login user and the destination user.

Login userDestination userRequired permissionsComment
DBA UserAny user-
Regular userSame user as loginCreate, drop and write table, create session
Regular userAny existing userCreate, drop and write ANY table, create sessionGrants can be provided on a system level by DBA or by target user directly
Regular userNot existing userCreate, drop and write ANY table, create user, create sessionGrants should be provided on a system level by DBA

We highly recommend creating an Airbyte-specific user for this purpose.

Setup guide​

You should now have all the requirements needed to configure Exasol as a destination in the UI. You'll need the following information to configure the Exasol destination:

  • Host
  • Port
  • Fingerprint of the Exasol server's TLS certificate (if the database uses a self-signed certificate)
  • Username
  • Password

Reference​

No configuration specification is available for this connector.

Changelog​

Expand to review
VersionDatePull RequestSubject
0.1.12023-02-21xxxFix the build
0.1.02023-01-??21200Initial version of the Exasol destination