-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
[AIRFLOW-XXXX] Move UPDATING changes into correct versions #7166
Conversation
388ee94
to
7d04742
Compare
UPDATING.md
Outdated
|
||
For example: `from airflow.operators.sensors import BaseSensorOperator` | ||
becomes `from airflow.sensors.base_sensor_operator import BaseSensorOperator` | ||
|
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.
This is still working on 1.10.7 too, so it was rightly placed in Master.
This deprecation would be for 2.0
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.
For reference, check: https://github.com/apache/airflow/blob/1.10.7/airflow/operators/__init__.py
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.
Got it, thanks! This is the one I had the most trouble finding. I'll move it back to Master
UPDATING.md
Outdated
### Renamed "extra" requirements for cloud providers | ||
|
||
Subpackages for specific services have been combined into one variant for | ||
each cloud provider. The name of the subpackage for the Google Cloud Platform | ||
has changed to follow style. | ||
|
||
If you want to install integration for Microsoft Azure, then instead of | ||
``` | ||
pip install 'apache-airflow[azure_blob_storage,azure_data_lake,azure_cosmos,azure_container_instances]' | ||
``` | ||
you should execute `pip install 'apache-airflow[azure]'` | ||
|
||
If you want to install integration for Amazon Web Services, then instead of | ||
`pip install 'apache-airflow[s3,emr]'`, you should execute `pip install 'apache-airflow[aws]'` | ||
|
||
If you want to install integration for Google Cloud Platform, then instead of | ||
`pip install 'apache-airflow[gcp_api]'`, you should execute `pip install 'apache-airflow[gcp]'`. | ||
The old way will work until the release of Airflow 2.1. |
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.
This is for Master. Not correct for 1.10.7
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.
It appears to be true in 1.10.7 for aws: https://github.com/apache/airflow/blob/1.10.7/setup.py#L154, and for gcp: https://github.com/apache/airflow/blob/1.10.7/setup.py#L220
(cherry-picked from 5d87491) and adapted to 1.10.* test branch
(cherry-picked from 5d87491) and adapted to 1.10.* test branch
(cherry-picked from 5d87491) and adapted to 1.10.* test branch
This PR moves some documentation within the UPDATING.md file to be tied to the appropriate versions for said changes. When we were migrating to 1.10.7 from 1.10.6 we were confused by which changes had been shipped with the most recent version. I went through all of the changes under
Airflow Master
in the file and tied the issues back to the changelog found here: https://airflow.apache.org/docs/stable/changelog.html. Those that were not present in the changelog under a specific version were left inAirflow Master
, but those that were present in a version were relocated to that version.Issue link:
Document only change, no JIRA issue
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]
. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX]
.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.
Read the Pull Request Guidelines for more information.