You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Andrew Chen (JIRA)" <ji...@apache.org> on 2017/04/12 01:16:41 UTC
[jira] [Created] (AIRFLOW-1101) Docs use the term "Pipelines"
instead of DAGs
Andrew Chen created AIRFLOW-1101:
------------------------------------
Summary: Docs use the term "Pipelines" instead of DAGs
Key: AIRFLOW-1101
URL: https://issues.apache.org/jira/browse/AIRFLOW-1101
Project: Apache Airflow
Issue Type: Improvement
Reporter: Andrew Chen
It's a bit confusing to use the words "DAGs" and "pipelines" interchangeably. Here are a couple examples where it is especially confusing.
https://airflow.incubator.apache.org/ui.html#code-view
"Transparency is everything. While the code for your pipeline is in source control, this is a quick way to get to the code that generates the DAG and provide yet more context."
https://airflow.incubator.apache.org/configuration.html#connections
"The pipeline code you will author will reference the ‘conn_id’ of the Connection objects."
"Connections in Airflow pipelines can be created using environment variables."
https://airflow.incubator.apache.org/configuration.html#scaling-out-with-celery
"If all your boxes have a common mount point, having your pipelines files shared there should work as well"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)