feature: exasol connector#1615
Conversation
|
Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA. In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR. CLA has not been signed by users: @marconae |
|
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
|
This repository enforces signed commits. Please sign your commits by following the docs here. |
marconae
force-pushed
the
feature/exasol-connector
branch
from
4f45b38 to
bf7cbe4
Compare
|
Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA. In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR. CLA has not been signed by users: @marconae |
marconae
force-pushed
the
feature/exasol-connector
branch
from
bf7cbe4 to
ffa7fd0
Compare
|
Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA. In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR. CLA has not been signed by users: @marconae |
felipecrv
left a comment
felipecrv
left a comment
There was a problem hiding this comment.
Thank you!
Can you please sign the CLA?
| DuckDB(Box<DuckDbConfig>), | ||
| // Hive, | ||
| // Exasol, | ||
| // Exasol, // TODO: add ExasolDbConfig when profile schema is defined |
There was a problem hiding this comment.
We are trying to remove these schemas to simplify this step. dbt-auth should be enough. No need for these schemas. cc @VersusFacit
There was a problem hiding this comment.
Thanks for the context! Removed the TODO comment. The ExasolAuth implementation in dbt-auth already handles all authentication configuration, so there's no need for an ExasolDbConfig schema.
| const REDSHIFT_KEYS: [&str; 2] = ["REDSHIFT:type", "type_text"]; | ||
| const DUCKDB_KEYS: [&str; 2] = ["DUCKDB:type", "type_text"]; | ||
| const CLICKHOUSE_KEYS: [&str; 2] = ["CLICKHOUSE:type", "type_text"]; | ||
| const EXASOL_KEYS: [&str; 2] = ["EXASOL:type", "type_text"]; |
There was a problem hiding this comment.
Does the driver expose this in the metadata? It's very useful to us.
There was a problem hiding this comment.
I will look into apache/arrow-adbc#3449 and see whether I can make an upstream change to exarrow-rs. I will get back to you on this.
|
@felipecrv just signed the CLA. Will check your comment now... |
marconae
force-pushed
the
feature/exasol-connector
branch
from
ffa7fd0 to
c9b6a32
Compare
Add Exasol database support to dbt-fusion using exarrow-rs (v0.9.0), an ADBC-compatible driver for Exasol maintained by Exasol Labs. https://github.com/exasol-labs/exarrow-rs - Backend::Exasol and AdapterType::Exasol as independent variants - ExasolAuth module with username/password + TLS fingerprint support - Driver: adbc_driver_exasol via `dbc install exasol` - Integration test gated by ADBC_EXASOL_URI env var - 12 auth unit tests, integration test verified against Exasol Docker Contributed on behalf of Exasol.
marconae
force-pushed
the
feature/exasol-connector
branch
from
c9b6a32 to
193250a
Compare
|
Code already merged by @felipecrv |
2 participants
This PR adds Exasol database support to dbt-fusion (I am working at Exasol). The connector uses exasol-labs/exarrow-rs (v0.9.0), an ADBC-compatible driver for Exasol with Apache Arrow data format support, maintained by Exasol.
exarrow-rs is part of the ADBC Driver Foundry and can be installed via
dbc install exasol. Foundry repo is here adbc-drivers/exasoldbt-auth): Username/password authentication with TLS encryption, certificate validation toggle, certificate fingerprint pinning, and connection timeout support. Profile keys:host,port,user,password,schema,encryption,certificate_validation,certificate_fingerprint,connection_timeout.Backend::ExasolandAdapterType::Exasoladded as independent variants across all match arms in dbt-xdbc, dbt-adapter, dbt-schemas, dbt-init, and dbt-df-providers.adbc_driver_exasollibrary with standardAdbcDriverInitentrypoint. Installable viadbc install exasol.statement_execute_exasolgated byADBC_EXASOL_URIenv var, verified against Exasol Docker.This PR is created in collaboration with Claude Code. The PR is raised on behalf of Exasol.