Skip to content
DocumentationIngest data
Ingest data
Integrations
Airbyte

Airbyte

Airbyte is an open-source data integration platform that can sync data from hundreds of sources into Altertable. Use our custom Altertable destination connector to load data directly into your Altertable lakehouse.

Goal

Install the custom Altertable destination in Airbyte, connect it to a lakehouse catalog, and verify a source sync with SQL.

Prerequisites

  • An Airbyte instance that allows custom Docker connectors.
  • Your lakehouse username and password from API keys & credentials in your organization settings.
  • The target Altertable catalog and schema names.
  • An Airbyte source ready to sync.

Steps

1. Add the Docker connector

The Altertable destination connector is available as a Docker image and can be added as a custom connector in your Airbyte instance.

ghcr.io/altertable-ai/airbyte-destination-altertable

  1. In your Airbyte instance, go to Settings → Destinations.
  2. Choose New connector → Add a new Docker connector.
  3. Enter Altertable as the display name.
  4. Enter ghcr.io/altertable-ai/airbyte-destination-altertable as the Docker repository name.
  5. Set the Docker image tag to latest, or use a pinned release tag.

2. Configure the destination

In the Airbyte destination settings, enter the lakehouse credentials below, along with the catalog name and schema where you want to sync data.

LAKEHOUSE_USERNAME="YOUR_LAKEHOUSE_USERNAME"
LAKEHOUSE_PASSWORD="YOUR_LAKEHOUSE_PASSWORD"

To use custom lakehouse credentials, create them in API keys & credentials in your organization settings.

3. Create and run a connection

Select the Altertable destination when creating or editing an Airbyte connection. Choose a source and run the first sync.

Verification

After Airbyte reports that the sync finished, query one of the synced tables with its fully qualified name:

SELECT *
FROM your_catalog.your_schema.your_table
LIMIT 10;

Confirm that the returned columns and rows match the selected Airbyte stream.

Troubleshooting

  • Airbyte cannot pull the connector: confirm that the Airbyte host can access ghcr.io and that the repository and tag are correct.
  • The destination check fails: copy the lakehouse username and password again from the target environment.
  • The sync writes to the wrong location: check the catalog and schema configured on the destination.
  • The sync completes but no rows appear: confirm that the source stream is selected and query the table name created by that stream.

Next steps

The connector source code is available at github.com/altertable-ai/airbyte-destination-altertable