sunank200 commented on code in PR #52196:
URL: https://github.com/apache/airflow/pull/52196#discussion_r2182278174
##########
task-sdk/docs/index.rst:
##########
@@ -46,47 +50,109 @@ Define a basic DAG and task in just a few lines of Python:
:end-before: [END simplest_dag]
:caption: Simplest DAG with :func:`@dag <airflow.sdk.dag>` and
:func:`@task <airflow.sdk.task>`
-Examples
---------
+2. Public Interface
+-------------------
+
+Direct metadata database access from task code is now restricted. A dedicated
Task Execution API handles all runtime interactions (state transitions,
heartbeats, XComs, and resource fetching), ensuring isolation and security.
+
+Airflow now supports a service-oriented architecture, enabling tasks to be
executed remotely via a new Task Execution API. This API decouples task
execution from the scheduler and introduces a stable contract for running tasks
outside of Airflow's traditional runtime environment.
+
+To support remote execution, Airflow provides the Task SDK — a lightweight
runtime environment for running Airflow tasks in external systems such as
containers, edge environments, or other runtimes. This lays the groundwork for
language-agnostic task execution and brings improved isolation, portability,
and extensibility to Airflow-based workflows.
+
+Airflow 3.0 also introduces a new ``airflow.sdk`` namespace that exposes the
core authoring interfaces for defining DAGs and tasks. DAG authors should now
import objects like :class:`airflow.sdk.DAG`, :func:`airflow.sdk.dag`, and
:func:`airflow.sdk.task` from ``airflow.sdk`` rather than internal modules.
This new namespace provides a stable, forward-compatible interface for DAG
authoring across future versions of Airflow.
+
+3. DAG Authoring Enhancements
+-----------------------------
+
+Writing your DAGs is now more consistent in Airflow 3.0. Use the stable
:mod:`airflow.sdk` interface to define your workflows and tasks.
+
+Why use ``airflow.sdk``?
+^^^^^^^^^^^^^^^^^^^^^^^^
+- Decouple your DAG definitions from Airflow internals (Scheduler, API Server,
etc.)
+- Enjoy a consistent API that won't break across Airflow upgrades
+- Import only the classes and decorators you need, without installing the full
Airflow core
+
+**Key imports from airflow.sdk**
+
+**Classes**
+
+- :class:`airflow.sdk.Asset`
Review Comment:
Added it
--
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]
