Skip to content

[FEATURE] Exasol integration - #12012

Open
abdullah094 wants to merge 1 commit into
fivetran:developfrom
abdullah094:feature/exasol-datasource
Open

[FEATURE] Exasol integration#12012
abdullah094 wants to merge 1 commit into
fivetran:developfrom
abdullah094:feature/exasol-datasource

Conversation

@abdullah094

Copy link
Copy Markdown
  • Added integration for the Exasol database.
  • Created a new data source for Exasol.
  • All unit tests have been run and passed.

@netlify

netlify Bot commented Aug 1, 2026

Copy link
Copy Markdown

👷 Deploy request for niobium-lead-7998 pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 9383684

@abdullah094

Copy link
Copy Markdown
Author

@cla-bot check

@abdullah094 abdullah094 changed the title [CONTRIB] Exasol integration [FEATURE] Exasol integration Aug 1, 2026
@joshua-stauffer

Copy link
Copy Markdown
Collaborator

Hi @abdullah094, thanks for the PR! I'd like to see a version of this merged, but want to get alignment at the design level first.

An RFC is required for new data sources (see CONTRIBUTING.md), but I realize that our PR template doesn't have that guidance. I'll fix it for the future, and this time we can continue the design discussion here on the PR.

I'd like to see Exasol supported in GX at the same level as Trino, Clickhouse, Teradata, Vertica, etc. The canonical path is for users to setup a SQLDatasource after installing via great_expectations[exasol]. The good news is that this approach will simplify the PR considerably! We can include Exasol in the data source compatibility reference, include install instructions in the docs, and run a core set of expectations against Exasol in CI. If there's sustained community demand, we can revisit adding a ExasolDatasource in the future.

If that approach is sounds ok to you, I'll detail the changes needed to get this PR merged! I also have a question about longer term maintenance: how actively is sqlalchemy-exasol maintained, and is it expected to track new Python and SQLAlchemy releases? I see that it's currently pinned to python >= 3.10, < 3.14, the same as GX. I expect those bounds to move on our side by October -- will sqlalchemy-exasol support python 3.14 by then?

@abdullah094 abdullah094 closed this Aug 4, 2026
@abdullah094 abdullah094 reopened this Aug 4, 2026
@abdullah094

Copy link
Copy Markdown
Author

Hello and thanks for responding so quickly on this @joshua-stauffer

The canonical path sound like a good idea to start with. I would love for you to share the details to get those done and merge the PR.

sqlalchemy_exasol will eventually be updated to 3.14. Our team works on maintaining our tools regularly. I am not sure that this will be done till October. I don't know how big of an issue this is for you guys. If this is a make or break issue. I can bring this to the table in our next planning session.

@abdullah094

Copy link
Copy Markdown
Author

Update on the sqlalchemy-exasol

python 3.14 support has been implemented and will be launched by the end of this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants