Skip to content

Migrate exasol provider to pyexasol 2.x and remove the <2 cap #69123

Closed

Description

@potiuk

The "Upgrade important CI environment" automation (#68933) pulled pyexasol from 1.3.0 to 2.2.2 (a major release). pyexasol 2.x ships stricter type information, so mypy now reports 8 errors in providers/exasol/src/airflow/providers/exasol/hooks/exasol.py (e.g. ExaConnection vs Connection variable reuse in get_conn, execute() argument types, export_to_pandas query_params).

To keep the CI-tooling upgrade unblocked, #68933 caps pyexasol>=0.26.0,<2 in providers/exasol/pyproject.toml.

Follow-up work: adapt the exasol hook to pyexasol 2.x (separate the Airflow Connection and ExaConnection locals, fix execute/export_to_pandas call signatures), update tests, then remove the <2 cap and re-lock.

Acceptance: cap removed; exasol mypy and unit tests pass against pyexasol 2.x.


Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting

Activity

  1. hectar-glitches commented on Jun 30, 2026

    @hectar-glitches

    hi @potiuk @eladkal , i'd like to take this issue! I will start with running mypy against pyexasol 2.x to confirm the 8 error locations before submitting a fix.

  2. added a commit that references this issue on Aug 27, 2026
    2abb35e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions