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
The "Upgrade important CI environment" automation (#68933) pulled
pyexasolfrom 1.3.0 to 2.2.2 (a major release). pyexasol 2.x ships stricter type information, so mypy now reports 8 errors inproviders/exasol/src/airflow/providers/exasol/hooks/exasol.py(e.g.ExaConnectionvsConnectionvariable reuse inget_conn,execute()argument types,export_to_pandasquery_params).To keep the CI-tooling upgrade unblocked, #68933 caps
pyexasol>=0.26.0,<2inproviders/exasol/pyproject.toml.Follow-up work: adapt the exasol hook to pyexasol 2.x (separate the Airflow
ConnectionandExaConnectionlocals, fixexecute/export_to_pandascall signatures), update tests, then remove the<2cap 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