Skip to content

Use built-in exceptions for JDBC sqlalchemy connection extras - #70535

Open
mitre88 wants to merge 1 commit into
apache:mainfrom
mitre88:narrow-jdbc-hook-exceptions
Open

Use built-in exceptions for JDBC sqlalchemy connection extras#70535
mitre88 wants to merge 1 commit into
apache:mainfrom
mitre88:narrow-jdbc-hook-exceptions

Conversation

@mitre88

@mitre88 mitre88 commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Part of the ongoing clean-up of broad AirflowException usages (enforced by the check-no-new-airflow-exceptions ratchet), following the pattern of #66279.

JdbcHook.sqlalchemy_url raised AirflowException for two input-validation failures in the connection extras: a sqlalchemy_query that is not a dict (now TypeError) and a missing sqlalchemy_scheme (now ValueError). The known_airflow_exceptions.txt entry for the file drops from 2 to 0, and the two existing tests now assert the specific exception types and messages.


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Fable 5)

Generated-by: Claude Code (Fable 5) following the guidelines

A wrong type for sqlalchemy_query is a TypeError and a missing
sqlalchemy_scheme is a ValueError; both were raised as the broad
AirflowException the community is actively reducing. Follows the
clean-up pattern of apache#66279.
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.

1 participant