

#Airflow 2.0 github upgrade#
Status: WIP - we will continue releasing updates to upgrade check separately from 2.0 release. To make it easier for users to upgrade from 1.10 to 2.0, we should create a single upgrade-check command in 1.10 that checks the common incompatibilities. We released packages that will allow us to use operators/hooks from Airflow 2.0 in Airflow 1.10. In all steps, the user is assisted by migration guides and runtime warnings. Once the migration is successful the user can happily use Airflow 2.0.In the next step, the user installs the latest version of Airflow and will migrate the database - airflow db upgrade.This command checks for common incompatibility problems. When the user is on the latest Airflow 1.10 release, they can use the airflow upgrade-check command to see if they can migrate to the new Airflow version.


More information is available on the wiki:Īll tasks are collected in "Airflow 2.0rc1" milestone for RC1 and all remaining "administrative" tasks that do not require release are in "Airflow 2.0" milestone RoadmapĪpart from defining the scope of work, we should also complete these tasks. This will make it more transparent and friendly.
#Airflow 2.0 github code#
This ticket should not describe individual changes to the code but summarize information that active community members know, but new community members don't know but want to know. This is a meta-ticket, so I would ask committers and PMC members to keep it up-to-date so that everyone has easy access to up-to-date information. This new feature enables high availability, scalability and greater performance.I am creating this ticket to help follow this process and coordinate our activities. SchedulerĪ new feature for Airflow 2.0 is the option to provide multiple schedulers. More information here.įor our purposes we have chosen a Postgres backend.
#Airflow 2.0 github software#
Architecture Show/Hide DetailsĪll applications are packaged up using Docker to isolate the software from its env so that it works in different development environments. Place your dag files within dags/ and your plugins within plugins/. It may take a few minutes for the containers to finish starting up.CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESī60b1cf71c84 apache/airflow:2.1.2 "/usr/bin/dumb-init … " About a minute ago Up About a minute (healthy) 0.0.0.0:5555- >5555/tcp, :::5555- >5555/tcp, 8080/tcp airflow-docker_flower_1Ĭc8d0e7d4313 apache/airflow:2.1.2 "/usr/bin/dumb-init … " About a minute ago Up About a minute (healthy) 8080/tcp airflow-docker_airflow-scheduler_1ĭ8dd9720bffd apache/airflow:2.1.2 "/usr/bin/dumb-init … " About a minute ago Up About a minute (healthy) 8080/tcp airflow-docker_airflow-worker_1Ĩ887045f093e apache/airflow:2.1.2 "/usr/bin/dumb-init … " About a minute ago Up About a minute (healthy) 0.0.0.0:8080- >8080/tcp, :::8080- >8080/tcp airflow-docker_airflow-webserver_1Ĭf55784b4c05 postgres:13 "docker-entrypoint.s… " About a minute ago Up About a minute (healthy) 5432/tcp airflow-docker_postgres_1Į6b51c4d2d68 redis:latest "docker-entrypoint.s… " About a minute ago Up About a minute (healthy) 0.0.0.0:6379- >6379/tcp, :::6379- >6379/tcp airflow-docker_redis_1
