-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Add documentation for hybrid executor and ungate the feature #40701
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
Add documentation for hybrid executor and ungate the feature #40701
Conversation
Publicly "release" the hybrid executor feature, including: - Documentation - Remove feature flag - What's new/changelog? TODO
|
@eladkal Do I need to write any change log or what's new blurbs for this one? Let me know what you think. Also maybe a post for https://airflow.apache.org/blog/ (But that would be outside of this PR of course). |
I don't think it requires seperated blog entry but that is always welcome if you want to! |
ferruzzi
left a comment
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.
Nice. The pros and cons are a nice touch, and thanks for including the rendered version of the docs.
Thanks @eladkal! I may write a blog in the coming week, but for now I'll just add a newsfragment to this PR. |
I added a fragment @eladkal, let me know what you think |
potiuk
left a comment
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.
LGTM
|
Can this be merged @o-nikolas ? |
Hey! I was waiting for @syedahsn's executor metrics PR to be merged first. But he can always circle back and update these docs as part of his PR I suppose. |
…40701) Publicly "release" the multiple executor configuration feature (formerly hybrid), including: - Documentation - Remove feature flag - What's new/changelog
Publicly "release" the hybrid executor feature, including:
A rendered view of the docs can be seen below:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.