Add providers, operators, and hooks readmes#11829
Merged
ryw merged 3 commits intoapache:masterfrom Oct 27, 2020
Merged
Conversation
…perators, and hooks directories
Member
|
Just one EOF static check failiing :) |
Contributor
Author
|
Thanks @potiuk! Is that failing because I need to add a new line at the end of these files? |
|
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks$,^Build docs$,^Spell check docs$,^Backport packages$,^Checks: Helm tests$,^Test OpenAPI*. |
|
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks$,^Build docs$,^Spell check docs$,^Backport packages$,^Checks: Helm tests$,^Test OpenAPI*. |
ryw
approved these changes
Oct 27, 2020
|
|
||
| # Airflow Operators | ||
|
|
||
| Airflow operators are modules that represent a single, ideally idempotent task. They are arbiters of the logic that executes when your DAG runs. |
michalmisiewicz
pushed a commit
to michalmisiewicz/airflow
that referenced
this pull request
Oct 30, 2020
* Add readmes with relevant information for Airflow 2.0 to providers, operators, and hooks directories * Add newline to end of files * Remove hanging EOF empty line
szn
pushed a commit
to szn/airflow
that referenced
this pull request
Nov 1, 2020
* Add readmes with relevant information for Airflow 2.0 to providers, operators, and hooks directories * Add newline to end of files * Remove hanging EOF empty line
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
3 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.
It took me quite a while to piece together how exactly operators, hooks, and providers would be released and distributed in Airflow 2.0 and beyond from various mailing list threads, AIPs, and slack conversations. Hoping that adding a little bit of color to readmes in the relevant subdirectories will help users who may be less familiar with the maintenance of the project figure out how exactly the operators, hooks, and providers directories differ. Someone should give these a quick once-over to validate that my mental model is accurate.
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.