FIX: Allow override of HTTP method in run_method of LivyAsyncHook - #64150
Merged
Conversation
eladkal
approved these changes
Mar 24, 2026
… as test_run_get_method_with_success
vatsrahul1001
pushed a commit
that referenced
this pull request
Mar 25, 2026
…4150) * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Removed duplicate test_run_method_success as it is the same as test_run_get_method_with_success
aaron-y-chen
pushed a commit
to aaron-y-chen/airflow
that referenced
this pull request
Mar 30, 2026
…ache#64150) * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Removed duplicate test_run_method_success as it is the same as test_run_get_method_with_success
Suraj-kumar00
pushed a commit
to Suraj-kumar00/airflow
that referenced
this pull request
Apr 7, 2026
…ache#64150) * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Removed duplicate test_run_method_success as it is the same as test_run_get_method_with_success
abhijeets25012-tech
pushed a commit
to abhijeets25012-tech/airflow
that referenced
this pull request
Apr 9, 2026
…ache#64150) * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Allow override the method in run_method of LivyAsyncHook * refactor: Removed duplicate test_run_method_success as it is the same as test_run_get_method_with_success
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.
LivyAsyncHook ignores run_method HTTP method after refactor LivyAsyncHook.run_method now accepts a nullable method parameter and validates it, but never applies it to the underlying HttpAsyncHook. The new implementation always uses AsyncHttpSession.run, which selects the HTTP verb from the hook’s self.method property. Since LivyAsyncHook initializes self.method to POST and run_method no longer overrides it, calls that previously defaulted to GET (or explicitly requested GET/PUT/DELETE) are sent as POST. This is a functional regression that can cause incorrect requests or unintended state changes against the Livy API (e.g., get_batch_state now issues POST).
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.