Apache Airflow (Incubating)
Перейти к файлу
Maxime Beauchemin 54b361d2a1 [AIRFLOW-238] Make compatible with flask-admin 1.4.1
The new flask-admin==1.4.1 release on 2016-06-13 breaks the Airflow
release currently in Pypi (1.7.1.2). This fixes the edge case triggered
by this new release.

* Closes #1588 on github
2016-06-14 12:22:32 +02:00
.github Update PR template with instructions about JIRA 2016-05-02 18:44:36 -04:00
airflow [AIRFLOW-238] Make compatible with flask-admin 1.4.1 2016-06-14 12:22:32 +02:00
dags adding druid hook and operator 2015-07-13 19:17:13 +00:00
dev [AIRFLOW-213] Add "Closes #X" phrase to commit messages 2016-06-07 09:07:20 -04:00
docs Merge branch 'align_startdate' 2016-06-11 13:47:27 +02:00
scripts [AIRFLOW-142] setup_env.sh doesn't download hive tarball if hdp is specified as distro 2016-06-09 14:24:54 -07:00
tests [AIRFLOW-230] [HiveServer2Hook] adding multi statements support 2016-06-13 11:54:35 -07:00
.codecov.yml [AIRFLOW-209] Add scheduler tests and improve lineage handling 2016-06-03 14:58:12 +02:00
.coveragerc Omit contrib from coverage report 2015-12-10 12:42:19 -08:00
.gitignore Add a version view to display airflow version info 2016-05-19 06:24:34 +00:00
.landscape.yml Linting 2016-03-20 17:34:02 -07:00
.rat-excludes AIRFLOW-190 Add codecov and remove download count 2016-05-30 12:52:24 +02:00
.travis.yml AIRFLOW-190 Add codecov and remove download count 2016-05-30 12:52:24 +02:00
CHANGELOG.txt [AIRFLOW-52] 1.7.1 version bump and changelog 2016-05-19 10:56:59 -07:00
CONTRIBUTING.md Merge pull request #1283 from clickthisnick/chore-remove-trailing-spaces 2016-04-08 17:33:34 -04: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 [AIRFLOW-155] Documentation of Qubole Operator 2016-06-01 14:57:33 -07:00
TODO.md [AIRFLOW-112] no-op README change to close this jira's PR 2016-05-13 14:57:01 -07:00
UPDATING.md Use os.execvp instead of subprocess.Popen for the webserver 2016-04-21 16:23:11 +02: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
run_tox.sh now running travis on all DB backends 2015-11-16 11:21:21 +01:00
run_unit_tests.sh Add function to get configuration as dict, plus unit tests 2016-03-28 13:04:17 -04:00
setup.cfg Updating to the right license (apache2) in setup.cfg 2015-06-17 08:48:41 -07:00
setup.py [AIRFLOW-238] Make compatible with flask-admin 1.4.1 2016-06-14 12:22:32 +02:00
tox.ini Merge remote-tracking branch 'upstream/master' into minicluster 2016-03-20 10:20:43 +01:00

README.md

Airflow

PyPI version Build Status Coverage Status Code Health Requirements Status Documentation Join the chat at https://gitter.im/apache/incubator-airflow

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.

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.

Getting started

Please visit the Airflow Platform documentation for help with installing Airflow, getting a quick start, or a more complete tutorial.

For further information, please visit the Airflow Wiki.

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.

User Interface

  • DAGs: Overview of all DAGs in your environment.

  • Tree View: Tree representation of a DAG that spans across time.

  • Graph View: Visualization of a DAG's dependencies and their current status for a specific run.

  • Task Duration: Total time spent on different tasks over time.

  • Gantt View: Duration and overlap of a DAG.

  • Code View: Quick way to view source code of a DAG.

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.

Committers:

Currently officially using Airflow: