|
| 1 | +--- |
| 2 | +title: Exasol Hybrid Runner | Collate High-Performance Database |
| 3 | +description: Connect Exasol database to Collate using the Hybrid Runner. Deploy the ingestion agent in your environment for secure, private network metadata extraction. |
| 4 | +slug: /connectors/database/exasol/hybrid-runner |
| 5 | +sidebarTitle: Hybrid Runner |
| 6 | +--- |
| 7 | +import { ConnectorDetailsHeader } from '/snippets/components/ConnectorDetailsHeader/ConnectorDetailsHeader.jsx' |
| 8 | +import ExternalIngestionDeployment from '/snippets/connectors/external-ingestion-deployment.mdx' |
| 9 | +import TestConnection from '/snippets/connectors/test-connection.mdx' |
| 10 | +import IngestionScheduleAndDeploy from '/snippets/connectors/ingestion-schedule-and-deploy.mdx' |
| 11 | +import ConfigureIngestion from '/snippets/connectors/database/configure-ingestion.mdx' |
| 12 | +import AdvancedConfiguration from '/snippets/connectors/database/advanced-configuration.mdx' |
| 13 | +import { MetadataIngestionUi } from '/snippets/components/MetadataIngestionUi.jsx' |
| 14 | +import Related from '/snippets/connectors/database/related.mdx' |
| 15 | + |
| 16 | +<ConnectorDetailsHeader |
| 17 | +icon='/public/images/connectors/exasol.webp' |
| 18 | +name="Exasol" |
| 19 | +stage="PROD" |
| 20 | +availableFeatures={["Metadata"]} |
| 21 | +unavailableFeatures={["Query Usage", "Lineage", "Column-level Lineage", "Data Profiler", "Data Quality", "Owners", "dbt", "Tags", "Stored Procedures", "Sample Data", "Auto-Classification"]} /> |
| 22 | +In this section, we provide guides and references for using the Exasol connector. |
| 23 | +Configure and schedule Exasol metadata from the OpenMetadata UI: |
| 24 | +- [Requirements](#requirements) |
| 25 | +- [Metadata Ingestion](#metadata-ingestion) |
| 26 | +- [Troubleshooting](/connectors/database/exasol/troubleshooting) |
| 27 | +<ExternalIngestionDeployment /> |
| 28 | +<Card title="OpenMetadata 1.6.1 or later" href="/deployment" > |
| 29 | + To deploy OpenMetadata, check the Deployment guides. |
| 30 | + </Card> |
| 31 | +## Requirements |
| 32 | +The connector requires **Exasol version 7.1 or higher** to function correctly. Ensure your Exasol instance meets this minimum version requirement before proceeding. |
| 33 | +## Metadata Ingestion |
| 34 | +<MetadataIngestionUi connector={"Exasol"} selectServicePath={"/public/images/connectors/exasol/select-service.png"} addNewServicePath={"/public/images/connectors/exasol/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/exasol/service-connection.png"} /> |
| 35 | +# Connection Options |
| 36 | +<Steps> |
| 37 | +<Step title="Connection Options"> |
| 38 | +**Connection Scheme**: Specifies the SQLAlchemy driver scheme options required to connect to Exasol. |
| 39 | +**Username**: The username used to connect to the Exasol database. Ensure that this user has sufficient privileges to read all the metadata from Exasol. |
| 40 | +**Password**: The password associated with the user connecting to Exasol. |
| 41 | +**Host and Port**: Defines the host and port of the Exasol instance. Provide this as a string in the format `hostname:port`. For example: `localhost:8563` |
| 42 | +- If running the OpenMetadata ingestion in a Docker container and your services are hosted on `localhost`, use `host.docker.internal:8563`. |
| 43 | +**SSL/TLS Settings**: Specifies the mode or settings for SSL/TLS validation during the connection. Available options: |
| 44 | +**validate-certificate (Default)**: Enables Transport Layer Security (TLS) and validates the server certificate using system certificate stores. |
| 45 | +**ignore-certificate**: Enables Transport Layer Security (TLS) but disables validation of the server certificate. |
| 46 | +<Tip> |
| 47 | +- This mode should not be used in production. It is useful for testing with self-signed certificates. |
| 48 | +</Tip> |
| 49 | +**disable-tls**: Disables Transport Layer Security (TLS). Data is sent in plain text (no encryption). |
| 50 | +[!WARNING] |
| 51 | +This mode is not recommended for production and should only be used in debugging scenarios. |
| 52 | +<Tip> |
| 53 | +Ensure that the appropriate TLS setting is chosen based on your security and deployment requirements. |
| 54 | +</Tip> |
| 55 | +</Step> |
| 56 | +<AdvancedConfiguration /> |
| 57 | +<TestConnection /> |
| 58 | +<ConfigureIngestion /> |
| 59 | +<IngestionScheduleAndDeploy /> |
| 60 | +</Steps> |
| 61 | + |
| 62 | +<Tip> |
| 63 | +When using a **Hybrid Ingestion Runner**, any sensitive credential fields—such as passwords, API keys, or private keys—must reference secrets using the following format: |
| 64 | +``` |
| 65 | +password: secret:/my/database/password |
| 66 | +``` |
| 67 | +This applies **only to fields marked as secrets** in the connection form (these typically mask input and show a visibility toggle icon). |
| 68 | +For a complete guide on managing secrets in hybrid setups, see the [Hybrid Ingestion Runner Secret Management Guide](https://docs.getcollate.io/getting-started/day-1/hybrid-saas/hybrid-ingestion-runner#3.-manage-secrets-securely). |
| 69 | +</Tip> |
| 70 | + |
| 71 | +## Troubleshooting |
| 72 | + |
| 73 | +<Columns cols={2}> |
| 74 | + <Card |
| 75 | + title="Exasol Troubleshooting" |
| 76 | + href="/connectors/database/exasol/troubleshooting"> |
| 77 | + Learn more about how to troubleshoot common Exasol connector issues and resolve configuration or ingestion errors. |
| 78 | + </Card> |
| 79 | +</Columns> |
| 80 | + |
| 81 | +<Related /> |
0 commit comments