Apache Airflow (Incubating)
Перейти к файлу
Josh Marlow 48d59e6145 Slight editing of the installation documentation 2016-02-01 13:45:45 -05:00
airflow Merge pull request #868 from CloverHealth/encrypt_logs 2016-01-28 16:56:05 -08:00
dags adding druid hook and operator 2015-07-13 19:17:13 +00:00
docs Slight editing of the installation documentation 2016-02-01 13:45:45 -05:00
scripts Merge pull request #674 from bolkedebruin/systemd 2015-12-04 14:37:32 -08:00
tests Update unittest for TriggerDagRun after repair. 2016-01-23 13:45:17 -05:00
.coveragerc Omit contrib from coverage report 2015-12-10 12:42:19 -08:00
.coveralls.yml Adding coveralls file 2015-10-21 10:57:23 -07:00
.gitignore remove .idea, add unittests.db to .gitignore 2015-11-12 12:56:28 +01:00
.travis.yml Add openssh server 2015-11-28 10:15:42 +01:00
CONTRIBUTING.md adapts name and behaviour of WithLogger 2015-12-08 12:21:21 +01:00
COPYRIGHT.txt Switching to Apache license 2015-03-14 16:01:26 -07:00
LICENSE.txt Switching to Apache license 2015-03-14 16:01:26 -07:00
MANIFEST.in make upgrades for metadata database easier across the board 2015-08-23 05:40:43 +00:00
README.md Fixed Azkaban link 2016-02-01 13:27:33 -05:00
TODO.md [hotfix] fixing subdag not refreshing properly 2016-01-20 12:23:52 -08:00
init.sh Changing configuration scheme 2015-01-16 14:31:54 -08:00
migrations.sql 0.7 + migrations 2015-05-25 23:11:14 -04:00
requirements.txt merging with master 2016-01-15 16:07:14 +05:30
run_tox.sh now running travis on all DB backends 2015-11-16 11:21:21 +01:00
run_unit_tests.sh fix condition in run_unit_tests.sh + fix indent + remove duplicated loaded config 2015-12-04 12:00:43 +01:00
setup.cfg Updating to the right license (apache2) in setup.cfg 2015-06-17 08:48:41 -07:00
setup.py typos and xcom changes 2016-01-18 16:14:49 +05:30
tox.ini now running travis on all DB backends 2015-11-16 11:21:21 +01:00

README.md

Airflow

Join the chat at https://gitter.im/airbnb/airflow

Build Status Coverage Status pypi downloads

Airflow is a platform to programmatically author, schedule and monitor workflows.

When workflows are defined as code, they become more maintainable, versionable, testable, and collaborative.

![img] (http://i.imgur.com/6Gs4hxT.gif)

Use airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command line utilities make performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress, and troubleshoot issues when needed.

Beyond the Horizon

Airflow is not a data streaming solution. Tasks do not move data from one to the other (though tasks can exchange metadata!). Airflow is not in the Spark Streaming or Storm space, it is more comparable to Oozie or Azkaban.

Workflows are expected to be mostly static or slowly changing. You can think of the structure of the tasks in your workflow as slightly more dynamic than a database structure would be. Airflow workflows are expected to look similar from a run to the next, this allows for clarity around unit of work and continuity.

Principles

  • Dynamic: Airflow pipelines are configuration as code (Python), allowing for dynamic pipeline generation. This allows for writing code that instantiates pipelines dynamically.
  • Extensible: Easily define your own operators, executors and extend the library so that it fits the level of abstraction that suits your environment.
  • Elegant: Airflow pipelines are lean and explicit. Parameterizing your scripts is built into the core of Airflow using the powerful Jinja templating engine.
  • Scalable: Airflow has a modular architecture and uses a message queue to orchestrate an arbitrary number of workers. Airflow is ready to scale to infinity.

Who uses Airflow?

As the Airflow community grows, we'd like to keep track of who is using the platform. Please send a PR with your company name and @githubhandle if you may.

Currently officially using Airflow: