scr-oath commented on issue #33088:
URL: https://github.com/apache/airflow/issues/33088#issuecomment-1666111504
It seems like - I could be wrong - `task_id` could be enough to get the
exact xcom information.
So… if a `TaskInstance` is able to know how it was triggered - and, when
scheduled is datasets/files, have corresponding list or map of dataset to the
task_id that had it as an "outlet" that would be a reasonable solution to hook
up the guts that could use the existing constructs to just xcom_pull from there
as needed.
```
Pull XComs that optionally meet certain criteria.
:param key: A key for the XCom. If provided, only XComs with matching
keys will be returned. The default key is ``'return_value'``,
also
available as constant ``XCOM_RETURN_KEY``. This key is
automatically
given to XComs returned by tasks (as opposed to being pushed
manually). To remove the filter, pass *None*.
:param task_ids: Only XComs from tasks with matching ids will be
pulled. Pass *None* to remove the filter.
:param dag_id: If provided, only pulls XComs from this DAG. If *None*
(default), the DAG of the calling task is used.
:param map_indexes: If provided, only pull XComs with matching
indexes.
If *None* (default), this is inferred from the task(s) being
pulled
(see below for details).
:param include_prior_dates: If False, only XComs from the current
execution_date are returned. If *True*, XComs from previous dates
are returned as well.
```
--
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]
