uranusjr commented on PR #29608:
URL: https://github.com/apache/airflow/pull/29608#issuecomment-1442811804
I think your plan makes sense. So we’ll use this PR to implement
value-passing, and add path support in a later PR.
--
This is an automated message from the Apache Git Service.
To
uranusjr commented on PR #29608:
URL: https://github.com/apache/airflow/pull/29608#issuecomment-1441235817
By the way, the argument name can probably be shortened to just `--xcom` or
`--xcoms`?
--
This is an automated message from the Apache Git Service.
To respond to the message, please
uranusjr commented on PR #29608:
URL: https://github.com/apache/airflow/pull/29608#issuecomment-1441235340
Allowing a path makes sense to me. Since a JSON string has a pretty
distinctive shape (starts and ends with either brackets or braces depending on
which format we decide to use), I
uranusjr commented on PR #29608:
URL: https://github.com/apache/airflow/pull/29608#issuecomment-1437292418
Using JSON for this feels cumbersome to me. I don’t have a much better idea
though. Also we need to find a way to support custom backends that may not
store values as JSON.
--
This
