dstandish commented on code in PR #62554:
URL: https://github.com/apache/airflow/pull/62554#discussion_r2907680860


##########
airflow-core/src/airflow/executors/base_executor.py:
##########
@@ -415,30 +395,6 @@ def trigger_tasks(self, open_slots: int) -> None:
             if key in self.attempts:
                 del self.attempts[key]
 
-            if isinstance(workload, workloads.ExecuteTask) and 
hasattr(workload, "ti"):
-                ti = workload.ti
-
-                # If it's None, then the span for the current id hasn't been 
started.
-                if self.active_spans is not None and 
self.active_spans.get("ti:" + str(ti.id)) is None:
-                    if isinstance(ti, TaskInstanceDTO):
-                        parent_context = 
Trace.extract(ti.parent_context_carrier)
-                    else:
-                        parent_context = 
Trace.extract(ti.dag_run.context_carrier)
-                    # Start a new span using the context from the parent.
-                    # Attributes will be set once the task has finished so 
that all
-                    # values will be available (end_time, duration, etc.).
-
-                    span = Trace.start_child_span(
-                        span_name=f"{ti.task_id}",
-                        parent_context=parent_context,
-                        component="task",
-                        start_as_current=False,
-                    )
-                    self.active_spans.set("ti:" + str(ti.id), span)
-                    # Inject the current context into the carrier.
-                    carrier = Trace.inject()
-                    ti.context_carrier = carrier

Review Comment:
   yeah see before i guess there was a span created for the task in the 
scheduler and this carrier represented that. but here we don't rely on the 
scheduler to create a span for the task --- the task creates it as a child of 
the dag run span



-- 
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]

Reply via email to