dstandish commented on code in PR #73875: URL: https://github.com/apache/airflow/pull/73875#discussion_r4149058825
########## airflow-core/docs/authoring-and-scheduling/language-sdks/index.rst: ########## @@ -22,31 +22,40 @@ Non-Python Task SDKs |experimental| -Airflow Dags are always defined in Python, but individual task *implementations* can be written in other -languages. When a task runs, Airflow's worker calls out the target language to execute the task logic, which -communicates the result back. The Dag author uses a lightweight Python *stub* to declare where the task lives; -everything else, including the actual business logic, Airflow API calls, and any library dependencies, lives -in a non-Python implementation. +Airflow Dags and tasks can be written in languages other than Python. A language SDK is used in one of two +ways: + +* **Native Dags.** The whole Dag, with its schedule, tasks and dependencies, is declared in the SDK's language. + See :ref:`language-sdks/native-dags`. +* **Mixed-language tasks.** A Python Dag declares the tasks and their dependencies, and the SDK implements some Review Comment: this reads wrong to me because a task can only ever be written in one language though sure we might need to stub it wherever we are _defining_ the dag. but that doesn't make it mixed-language IMO -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
