-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Databricks: add more methods to represent run state information #19723
Conversation
60e0747
to
d607df5
Compare
d607df5
to
052b9f6
Compare
052b9f6
to
30aefea
Compare
Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
…nto databricks-issue-19357
run_state_str = ( | ||
f"State: {state.life_cycle_state}. Result: {state.result_state}. {state.state_message}" | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about putting this in RunState
’s __str__
and just call str(state)
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That’s primarily because I’m not sure if it may break something inside airflow. I’m not expert in it (yet)
The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
This PR adds a warning about need to use XCOM if
get_run_state
function is used, plus adds more methods to retrieve information about run statecloses: #19357