Use built-in exceptions for Postgres hook input validation - #70537
Open
mitre88 wants to merge 1 commit into
Open
Use built-in exceptions for Postgres hook input validation#70537mitre88 wants to merge 1 commit into
mitre88 wants to merge 1 commit into
Conversation
A wrong type for sqlalchemy_query is a TypeError, and requesting the psycopg3-unsupported realdictcursor is a ValueError like the invalid cursor branch right next to it; both were raised as the broad AirflowException the community is actively reducing. Follows the clean-up pattern of apache#66279.
potiuk
added
the
ready for maintainer review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the ongoing clean-up of broad
AirflowExceptionusages (enforced by thecheck-no-new-airflow-exceptionsratchet), following the pattern of #66279.PostgresHookraisedAirflowExceptionfor two input-validation failures: asqlalchemy_queryconnection extra that is not a dict (nowTypeError), and requestingrealdictcursorwith psycopg3 (nowValueError, matching the invalid-cursor branch immediately below it that already raisesValueError). Theknown_airflow_exceptions.txtentry for the file drops from 2 to 0, and the existing test now asserts the specific exception type and message.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5) following the guidelines