AIP-69: Adding Edge Provider Package for Edge Executor / Worker #41729
Conversation
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
This was referenced Aug 25, 2024
jscheffl
requested review from
hussein-awala,
kaxil,
o-nikolas,
shahar1 and
vikramkoka
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
from
e344b38 to
64c0543
Compare
jscheffl
changed the title
potiuk
reviewed
Sep 1, 2024
Member
|
Maybe we can further split that one? It's a huge one |
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
from
64c0543 to
6c6f62d
Compare
This was referenced Sep 5, 2024
Contributor
Author
Yeah but actually... all individual pieces are pretty "simple". Please have a look to the 6 split PRs I cut from this. Needed to cumulate a bit to make tests working with dependencies between the slices though... each PR check only the last commit or in order once merged the LoC is reducing if we rebase incrementally. |
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
from
6c6f62d to
cc4fdcd
Compare
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
3 times, most recently
from
4cf6fc4 to
70a5431
Compare
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
from
1323570 to
0e064bf
Compare
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
2 times, most recently
from
36a96bc to
34ec403
Compare
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
2 times, most recently
from
43bb51a to
4538ff5
Compare
(cherry picked from commit 4e9c2262f567a2511d02d4acd43b821fa0df45d2)
jscheffl
force-pushed
the
feature/aip-69-remote-executor-provider
branch
from
4538ff5 to
5a7fe9d
Compare
Contributor
Author
|
All pieces of the PR were merged individually, this is now done implicitly! |
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.
After a PoC in PR #40224 and the ongoing implementation which in total as "Mothership" was tracked in PR #40900 here is the AIP-69 MVP Implementation PR.
UPDATE: After completion of the discussion the "Remote Executor" was now renamed to "Edge Executor" in the PR.
This PR contains all files needed to make the provider package for AIP-69 a MVP == Minimum Viable Product. Besides (only) provider files the core adjustments are contained which are needed to make CI happy.
As greed in the AIP-69 vote the Edge provider will be marked as pre-release and as experimental. Also docs are pointing to this.
As it is a MVP, it can be started to be experienced and functions are limited to the bare minimum. But as something that is working, further functions can be added. Status of implementation is tracked in
docs/apache-airflow-providers-edge/edge_executor.rstwhere also limitations are listed.As this is a split for the provider-only files as PR from the overall PR #40900, there are two PRs completing the set which are tracked separately:
If you want to have something "testable" being running, please use descriptions and code from PR #40900
FYI @clellmann @wolfdn @AutomationDev85 @OliverWannenwetsch