Skip to end of metadataGo to start of metadata
The purpose of an Airflow Improvement Proposal (AIP) is to introduce any major change to Apache Airflow. This is required in order to balance the need to support new features, use cases, while avoiding accidentally introducing half thought-out interfaces that cause needless problems when changed.
What is considered a major change that needs an AIP?
See the License for the # specific language governing permissions and limitations # under the License. Import json from typing import Any, Dict, List, Optional from airflow.models import BaseOperator from airflow.providers.slack.hooks.slack import SlackHook from airflow.utils.decorators import applydefaults.
Any of the following should be considered a major change:
- Apache Airflow is a tool for describing, executing, and monitoring workflows. At Slack, we use Airflow to orchestrate and manage our data warehouse workflows, which includes product and business metrics and also is used for different engineering use-cases (e.g. Search and offline indexing).
- Join the Apache Airflow slack. After creating account in slack you can join #troubleshooting and #development where you can look for help in using and developing Airflow respectively. Ask at the devlist, see 'Join the devlist' link above; Check Stack Overflow.
- Apache Airflow is an open-source data workflow management project originally created at Airbnb in 2014. In terms of data workflows it covers, we can think about the following sample use cases: 🚀.
- Any major new feature, subsystem, or piece of functionality
- Any change that impacts the public interfaces of the project
What are the 'public interfaces' of the project? All of the following are public interfaces that people build around:
- Airflow DAG DSL components: DAG, XCom, TaskInstance and context.
- Web UI
- Core operators (BaseOperator, SubDagOperator, SensorOperator)
- [Airflow 2.0] REST endpoints
- Command line tools and arguments
Proposal lifecycle
Discuss
Most proposals start with an idea. If you have an idea of how Airflow could improve, we encourage you to send an email to dev@airflow.apache.org with a subject starting with [DISCUSS]. This email thread will allow you to gather early feedback. We encourage you to start a Draft document or share a Google Document with the mailing list detailing your proposal. Use AIP template here to file details on your proposal.
Draft
Anyone is welcome to propose a new Improvement to Airflow. You will need to request edit access to the Confluence page in order to create your AIP document. You can do so by sending an email with your Wiki ID to dev@airflow.apache.org and request permission.
Vote
Once you or someone else feels like there's a rough consensus on the idea and there's no strong opposition, you can move your proposal to the Vote phase. For this you will send a new email to the dev list with the subject starting with [VOTE]. This phase follows a vote on code modifications for Apache projects as described here. Remember to link the discussion thread to your AIP and ideally also to this vote email. And don't forget to link the AIP to the email as well.
The voting has to last at least 72 hours and it's a good practice to extend this time if most of this period is a weekend. Whole community is encouraged to give +1 and -1 votes. There's also fractional votes (0.5, -0.99) that allow you to express your view on the discussion without giving an explicit approval/block signal. However, only Airflow committers and PMC members have a binding vote. This means that any vote requires at least 3, +1 binding votes to be recognized as passed. In addition, any -1 binding vote will move the proposal back to the Discuss phase in order to address changes.
PetTracer is an ultra-light GPS collar designed specifically for cats. Built from the ground up to be a safe and comfortable collar with one mission – to be able to locate your cat whenever you. Meet the Whistle GO Family. The Best Pet Tracker Just Got Better Introducing Whistle GO & Whistle GO Explore, our latest, best-in-class pet health & location trackers. Know more about your pet. Pet tracker app.
The vote is a consensus-seeking process, 'the goal is not to *win* votes or come to a unanimous agreement, but rather to ensure that there's a forum for people to raise and discuss their concerns, and that nobody feels strongly enough to block the group from moving forward. Consensus-seeking emphasizes discussion over enumeration: *Rough consensus is achieved when all issues are addressed, but not necessarily accommodated.*' (quote from Working in Public: The Making and Maintenance of Open Source Softwareby Nadia Eghbal)
If you want to introduce significant changes to your proposal after it has been accepted you can do so following the same procedure.
Accepted
Congratulations! Your proposal has been accepted. Next up is breaking down tasks. You should break down tasks on Apache Airflow GitHub issues page. You can optionally group the tasks together in a Github Project if it consists of multiple steps and you want to be able to track progress for its implementation or share the progress with others. Once issues are created, make sure to send them to the vote thread (optionally Airflow slack). Ask a committer to create a label for your AIP and link all your issues with it for easier searchability.
Now you can start contributing and - more importantly - you can, and probably should, encourage others to contribute to your project. However this is optional and up to your discretion. You can learn how to contribute and communicate by reading the Contributing guide in the GitHub repository. Use your imagination and various communication channels for ways to encourage people if you do not already have contributors following your idea. Best free blu ray to mkv converter. It is advisable that several people work on the AIP so that the knowledge is shared.
Completed
You should move your AIP to complete after you consider the main bulk of work has been merged to the repository. It is okay to leave open issues for minor follow up tasks like adding additional capabilities or similar.
Abandoned
AIP may be moved to abandoned if there has been no owner or intention of developing it further for over a year or if the owner decides to abandon it. The latter can happen if the creator decides to refactor AIP into a new AIP for example or if there is a proposal that supersedes the original AIP.
Completed AIPs
Accepted AIPs
AIPs which have been voted on and accepted for inclusion in Airflow, but not yet (fully) implemented.
AIPs under discussion
Abandoned AIPs
(The above list is automatically generated based on page labels. Do not edit manually)
Released:
Provider package apache-airflow-providers-slack for Apache Airflow
Project description
Apache Airflow Book
Package apache-airflow-providers-slack
Release: 3.0.0
Provider package
This is a provider package for slack provider. All classes for this provider packageare in airflow.providers.slack python package.
You can find package information and changelog for the providerin the documentation.
Installation
NOTE!
On November 2020, new version of PIP (20.3) has been released with a new, 2020 resolver. This resolverdoes not yet work with Apache Airflow and might lead to errors in installation - depends on your choiceof extras. In order to install Airflow you need to either downgrade pip to version 20.2.4pip install --upgradepip20.2.4 or, in case you use Pip 20.3, you need to add option--use-deprecatedlegacy-resolver to your pip install command.
You can install this package on top of an existing airflow 2.* installation viapip install apache-airflow-providers-slack
PIP requirements
| PIP package | Version required |
|---|---|
| slack_sdk | >=3.0.0,<4.0.0 |
Any of the following should be considered a major change:
- Apache Airflow is a tool for describing, executing, and monitoring workflows. At Slack, we use Airflow to orchestrate and manage our data warehouse workflows, which includes product and business metrics and also is used for different engineering use-cases (e.g. Search and offline indexing).
- Join the Apache Airflow slack. After creating account in slack you can join #troubleshooting and #development where you can look for help in using and developing Airflow respectively. Ask at the devlist, see 'Join the devlist' link above; Check Stack Overflow.
- Apache Airflow is an open-source data workflow management project originally created at Airbnb in 2014. In terms of data workflows it covers, we can think about the following sample use cases: 🚀.
- Any major new feature, subsystem, or piece of functionality
- Any change that impacts the public interfaces of the project
What are the 'public interfaces' of the project? All of the following are public interfaces that people build around:
- Airflow DAG DSL components: DAG, XCom, TaskInstance and context.
- Web UI
- Core operators (BaseOperator, SubDagOperator, SensorOperator)
- [Airflow 2.0] REST endpoints
- Command line tools and arguments
Proposal lifecycle
Discuss
Most proposals start with an idea. If you have an idea of how Airflow could improve, we encourage you to send an email to dev@airflow.apache.org with a subject starting with [DISCUSS]. This email thread will allow you to gather early feedback. We encourage you to start a Draft document or share a Google Document with the mailing list detailing your proposal. Use AIP template here to file details on your proposal.
Draft
Anyone is welcome to propose a new Improvement to Airflow. You will need to request edit access to the Confluence page in order to create your AIP document. You can do so by sending an email with your Wiki ID to dev@airflow.apache.org and request permission.
Vote
Once you or someone else feels like there's a rough consensus on the idea and there's no strong opposition, you can move your proposal to the Vote phase. For this you will send a new email to the dev list with the subject starting with [VOTE]. This phase follows a vote on code modifications for Apache projects as described here. Remember to link the discussion thread to your AIP and ideally also to this vote email. And don't forget to link the AIP to the email as well.
The voting has to last at least 72 hours and it's a good practice to extend this time if most of this period is a weekend. Whole community is encouraged to give +1 and -1 votes. There's also fractional votes (0.5, -0.99) that allow you to express your view on the discussion without giving an explicit approval/block signal. However, only Airflow committers and PMC members have a binding vote. This means that any vote requires at least 3, +1 binding votes to be recognized as passed. In addition, any -1 binding vote will move the proposal back to the Discuss phase in order to address changes.
PetTracer is an ultra-light GPS collar designed specifically for cats. Built from the ground up to be a safe and comfortable collar with one mission – to be able to locate your cat whenever you. Meet the Whistle GO Family. The Best Pet Tracker Just Got Better Introducing Whistle GO & Whistle GO Explore, our latest, best-in-class pet health & location trackers. Know more about your pet. Pet tracker app.
The vote is a consensus-seeking process, 'the goal is not to *win* votes or come to a unanimous agreement, but rather to ensure that there's a forum for people to raise and discuss their concerns, and that nobody feels strongly enough to block the group from moving forward. Consensus-seeking emphasizes discussion over enumeration: *Rough consensus is achieved when all issues are addressed, but not necessarily accommodated.*' (quote from Working in Public: The Making and Maintenance of Open Source Softwareby Nadia Eghbal)
If you want to introduce significant changes to your proposal after it has been accepted you can do so following the same procedure.
Accepted
Congratulations! Your proposal has been accepted. Next up is breaking down tasks. You should break down tasks on Apache Airflow GitHub issues page. You can optionally group the tasks together in a Github Project if it consists of multiple steps and you want to be able to track progress for its implementation or share the progress with others. Once issues are created, make sure to send them to the vote thread (optionally Airflow slack). Ask a committer to create a label for your AIP and link all your issues with it for easier searchability.
Now you can start contributing and - more importantly - you can, and probably should, encourage others to contribute to your project. However this is optional and up to your discretion. You can learn how to contribute and communicate by reading the Contributing guide in the GitHub repository. Use your imagination and various communication channels for ways to encourage people if you do not already have contributors following your idea. Best free blu ray to mkv converter. It is advisable that several people work on the AIP so that the knowledge is shared.
Completed
You should move your AIP to complete after you consider the main bulk of work has been merged to the repository. It is okay to leave open issues for minor follow up tasks like adding additional capabilities or similar.
Abandoned
AIP may be moved to abandoned if there has been no owner or intention of developing it further for over a year or if the owner decides to abandon it. The latter can happen if the creator decides to refactor AIP into a new AIP for example or if there is a proposal that supersedes the original AIP.
Completed AIPs
Accepted AIPs
AIPs which have been voted on and accepted for inclusion in Airflow, but not yet (fully) implemented.
AIPs under discussion
Abandoned AIPs
(The above list is automatically generated based on page labels. Do not edit manually)
Released:
Provider package apache-airflow-providers-slack for Apache Airflow
Project description
Apache Airflow Book
Package apache-airflow-providers-slack
Release: 3.0.0
Provider package
This is a provider package for slack provider. All classes for this provider packageare in airflow.providers.slack python package.
You can find package information and changelog for the providerin the documentation.
Installation
NOTE!
On November 2020, new version of PIP (20.3) has been released with a new, 2020 resolver. This resolverdoes not yet work with Apache Airflow and might lead to errors in installation - depends on your choiceof extras. In order to install Airflow you need to either downgrade pip to version 20.2.4pip install --upgradepip20.2.4 or, in case you use Pip 20.3, you need to add option--use-deprecatedlegacy-resolver to your pip install command.
You can install this package on top of an existing airflow 2.* installation viapip install apache-airflow-providers-slack
PIP requirements
| PIP package | Version required |
|---|---|
| slack_sdk | >=3.0.0,<4.0.0 |
Cross provider package dependencies
Those are dependencies that might be needed in order to use all the features of the package.You need to install the specified backport providers package in order to use them.
You can install such cross-provider dependencies when installing from PyPI. For example:
Apache Airflow Stackoverflow
| Dependent package | Extra |
|---|---|
| apache-airflow-providers-http | http |
Release historyRelease notifications | RSS feed
3.0.0
3.0.0rc1 pre-release
2.0.0
2.0.0rc1 pre-release
1.0.0
1.0.0rc1 pre-release
1.0.0b2 pre-release
1.0.0b1 pre-release
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Files for apache-airflow-providers-slack, version 3.0.0| Filename, size | File type | Python version | Upload date | Hashes |
|---|---|---|---|---|
| Filename, size apache_airflow_providers_slack-3.0.0-py3-none-any.whl (18.9 kB) | File type Wheel | Python version py3 | Upload date | Hashes |
| Filename, size apache-airflow-providers-slack-3.0.0.tar.gz (15.0 kB) | File type Source | Python version None | Upload date | Hashes |
Hashes for apache_airflow_providers_slack-3.0.0-py3-none-any.whl
Hashes for apache_airflow_providers_slack-3.0.0-py3-none-any.whl| Algorithm | Hash digest |
|---|---|
| SHA256 | 6e906a0baccb5b24b052b0bd8bd3558c7949e4ef017500814b79f83c1f3e9f37 |
| MD5 | 7bc5c70d3d31876bfbfb82531c4596c5 |
| BLAKE2-256 | 6fdf8e7cd69285151c0ca37906020cc2159841d337606c5810dd11600ec58a2a |
Hashes for apache-airflow-providers-slack-3.0.0.tar.gz
Apache Airflow Pdf
Hashes for apache-airflow-providers-slack-3.0.0.tar.gz| Algorithm | Hash digest |
|---|---|
| SHA256 | 4a1f3fb5a14b695336b9dd5f9be67896e6a04bf0ad0cbbc5992f38ab78aa099f |
| MD5 | a4e48a09966469ab21e23eed6c90adef |
| BLAKE2-256 | 5475d17e35d74d590dc36145d2789a29201b3d73e36953ec4f700ea4a3a456a0 |
