You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -167,31 +167,80 @@ unit of work and continuity.
167
167

168
168
169
169
170
-
## Using hooks and Operators from "master" in Airflow 1.10
170
+
## Backport packages: Using providers from Airflow 2.0 in Airflow 1.10.*
171
171
172
-
Currently, stable versions of Apache Airflow are released in 1.10.* series. We are working on the
173
-
future, major version of Airflow from the 2.0.* series. It is going to be released in 2020. However, the exact time of release depends on many factors and is yet unknown.
174
-
We have already a lot of changes in the hooks/operators/sensors for many external systems
175
-
and they are not used because they are part of the master/2.0 release.
172
+
Currently, stable Apache Airflow versions are from the 1.10.* series.
173
+
We are working on the future, major version of Airflow from the 2.0.* series.
174
+
It is going to be released in 2020. However, the exact time of release depends on many factors and is
175
+
not yet confirmed.
176
176
177
-
In the Airflow 2.0 - following AIP-21 "change in import paths" all the non-core operators/hooks/sensors
178
-
of Apache Airflow have been moved to the "airflow.providers" package. This opened a possibility to
179
-
use the operators from Airflow 2.0 in Airflow 1.10 - with the constraint that those
180
-
packages can only be used in python3.6+ environment.
177
+
We have already a lot of changes in the operators, transfers, hooks, sensors, secrets for many external
178
+
systems, but they are not used nor tested widely because they are part of the master/2.0 release.
181
179
182
-
Therefore we decided to prepare and release backport packages that can be installed
183
-
for older Airflow versions. Those backport packages are released more frequently. Users do not
184
-
have to upgrade their Airflow version to use those packages. There are a number of changes
185
-
between Airflow 2.0 and 1.10.* - documented in [UPDATING.md](UPDATING.md). With backported
186
-
providers package users can migrate their DAGs to the new providers package incrementally
180
+
In the Airflow 2.0 - following AIP-21 "change in import paths" all the non-core interfaces to external
181
+
systems of Apache Airflow have been moved to the "airflow.providers" package.
182
+
183
+
Thanks to that and automated backport effort we took, the operators from Airflow 2.0
184
+
can be used in Airflow 1.10 as separately installable packages, with the constraint that
185
+
those packages can only be used in python3.6+ environment.
186
+
187
+
We released backport packages that can be installed for older Airflow versions.
188
+
Those backport packages are going to be released more frequently that main Airflow 1.10.& releases.
189
+
190
+
You will not have to upgrade your Airflow version to use those packages. You can find those packages in the
191
+
[PyPI](https://pypi.org/search/?q=apache-airflow-backport-providers&o=) and install them separately for each
192
+
provider.
193
+
194
+
Those packages are available now and can be used in the latest Airflow 1.10* version. Most of those
195
+
packages are also installable and usable in most Airflow 1.10.* releases but there is no extensive testing
196
+
done beyond the latest released version, so you might expect more problems in earlier Airflow versions.
197
+
198
+
Releasing the backport packages is also a way to ease migration to 2.0.
199
+
200
+
With backported providers package users can migrate their DAGs to the new providers package incrementally
187
201
and once they convert to the new operators/sensors/hooks they can seamlessly migrate their
188
-
environments to Airflow 2.0.
202
+
environments to Airflow 2.0. The nice thing about providers backport packages is that you can use
203
+
both old and new classes at the same time - even in the same DAG. So your migration can be gradual and smooth.
204
+
Note that in Airflow 2.0 old classes raise deprecation warning and redirect to the new classes wherever
205
+
it is possible. In some rare cases the new operators will not be fully backwards compatible - you will find
206
+
information about those cases in [UPDATING.md](UPDATING.md) where we explained all such cases. Switching
207
+
early to the Airflow 2.0 operators while still running Airflow 1.10 will make your migration much easier.
189
208
190
209
More information about the status and releases of the back-ported packages are available
191
210
at [Backported providers package page](https://cwiki.apache.org/confluence/display/AIRFLOW/Backported+providers+packages+for+Airflow+1.10.*+series)
192
211
193
-
Dependencies between packages are stored in ``airflow/providers/dependencies.json``. See
|[40bf8f28f](https://github.com/apache/airflow/commit/40bf8f28f97f17f40d993d207ea740eba54593ee)| 2020-06-18 | Detect automatically the lack of reference to the guide in the operator descriptions (#9290) |
|[40bf8f28f](https://github.com/apache/airflow/commit/40bf8f28f97f17f40d993d207ea740eba54593ee)| 2020-06-18 | Detect automatically the lack of reference to the guide in the operator descriptions (#9290) |
|[0b0e4f7a4](https://github.com/apache/airflow/commit/0b0e4f7a4cceff3efe15161fb40b984782760a34)| 2020-05-26 | Preparing for RC3 relase of backports (#9026) |
8
9
|[00642a46d](https://github.com/apache/airflow/commit/00642a46d019870c4decb3d0e47c01d6a25cb88c)| 2020-05-26 | Fixed name of 20 remaining wrongly named operators. (#8994) |
|[0b0e4f7a4](https://github.com/apache/airflow/commit/0b0e4f7a4cceff3efe15161fb40b984782760a34)| 2020-05-26 | Preparing for RC3 relase of backports (#9026) |
111
114
|[00642a46d](https://github.com/apache/airflow/commit/00642a46d019870c4decb3d0e47c01d6a25cb88c)| 2020-05-26 | Fixed name of 20 remaining wrongly named operators. (#8994) |
|[0b0e4f7a4](https://github.com/apache/airflow/commit/0b0e4f7a4cceff3efe15161fb40b984782760a34)| 2020-05-26 | Preparing for RC3 relase of backports (#9026) |
8
9
|[00642a46d](https://github.com/apache/airflow/commit/00642a46d019870c4decb3d0e47c01d6a25cb88c)| 2020-05-26 | Fixed name of 20 remaining wrongly named operators. (#8994) |
|[0b0e4f7a4](https://github.com/apache/airflow/commit/0b0e4f7a4cceff3efe15161fb40b984782760a34)| 2020-05-26 | Preparing for RC3 relase of backports (#9026) |
141
144
|[00642a46d](https://github.com/apache/airflow/commit/00642a46d019870c4decb3d0e47c01d6a25cb88c)| 2020-05-26 | Fixed name of 20 remaining wrongly named operators. (#8994) |
0 commit comments