You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/08/07 09:52:10 UTC

[GitHub] [airflow] mutiev opened a new pull request, #25577: Documentation update. Actualizing passing data options

mutiev opened a new pull request, #25577:
URL: https://github.com/apache/airflow/pull/25577

   TaskFlow API adds new pass data options
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] boring-cyborg[bot] commented on pull request #25577: Documentation update. Actualizing passing data options

Posted by GitBox <gi...@apache.org>.

boring-cyborg[bot] commented on PR #25577:
URL: https://github.com/apache/airflow/pull/25577#issuecomment-1207435749

   Awesome work, congrats on your first merged pull request!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] potiuk merged pull request #25577: Documentation update. Actualizing passing data options

Posted by GitBox <gi...@apache.org>.

potiuk merged PR #25577:
URL: https://github.com/apache/airflow/pull/25577


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] boring-cyborg[bot] commented on pull request #25577: Documentation update. Actualizing passing data options

Posted by GitBox <gi...@apache.org>.

boring-cyborg[bot] commented on PR #25577:
URL: https://github.com/apache/airflow/pull/25577#issuecomment-1207370597

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:
- Pay attention to the quality of your code (flake8, mypy and type annotations). Our [pre-commits]( https://github.com/apache/airflow/blob/main/STATIC_CODE_CHECKS.rst#prerequisites-for-pre-commit-hooks) will help you with that.
- In case of a new feature add useful documentation (in docstrings or in `docs/` directory). Adding a new operator? Check this short [guide](https://github.com/apache/airflow/blob/main/docs/apache-airflow/howto/custom-operator.rst) Consider adding an example DAG that shows how users should use it.
- Consider using [Breeze environment](https://github.com/apache/airflow/blob/main/BREEZE.rst) for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
- Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
- Please follow [ASF Code of Conduct](https://www.apache.org/foundation/policies/conduct) for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
- Be sure to read the [Airflow Coding style]( https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#coding-style-and-best-practices).
Apache Airflow is a community-driven project and together we are making it better 🚀.
In case of doubts contact the developers at:
Mailing List: dev@airflow.apache.org
Slack: https://s.apache.org/airflow-slack

--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] potiuk commented on a diff in pull request #25577: Documentation update. Actualizing passing data options

Posted by GitBox <gi...@apache.org>.

potiuk commented on code in PR #25577:
URL: https://github.com/apache/airflow/pull/25577#discussion_r939640405


##########
docs/apache-airflow/concepts/overview.rst:
##########
@@ -74,12 +74,14 @@ Or, with the ``set_upstream`` and ``set_downstream`` methods::
 
 These dependencies are what make up the "edges" of the graph, and how Airflow works out which order to run your tasks in. By default, a task will wait for all of its upstream tasks to succeed before it runs, but this can be customized using features like :ref:`Branching <concepts:branching>`, :ref:`LatestOnly <concepts:latest-only>`, and :ref:`Trigger Rules <concepts:trigger-rules>`.
 
-To pass data between tasks you have two options:
+To pass data between tasks you have three options:
 
 * :doc:`xcoms` ("Cross-communications"), a system where you can have tasks push and pull small bits of metadata.
 
 * Uploading and downloading large files from a storage service (either one you run, or part of a public cloud)
 
+* TaskFlow API automatically passes data between tasks

Review Comment:
   ```suggestion
   * TaskFlow API automatically passes data between tasks via implicit :doc:`xcoms`
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org