On 2016-08-03 18:42, Joseph Napolitano wrote:
What I can say is that we use it a lot, but very lightly. We basically
use
it to communicate the S3 key for a flat file between operators.
Just to follow up on this: here's a Gist with some example usage based
on the "store in XCom" approach:
https://gist.github.com/anonymous/b41228011275fb362aa5b95b476de542
We're using a macro to make retrieval a little nicer, and the end result
is not too different from reading from {{ params }}.
Nevertheless, +1 for a more first-class approach, if possible. {{
dag_run.params.foo }}, anyone? ;-)
On a related note, out of curiosity: does someone have any information
on use case(s) where changes to dag.params are useful during a DAG run?
Or is that just a consequence of the fact that the DAG object is
instantiated multiple times during a single run?
Is there an implicit assumption that the values passed to the DAG object
are the same every time within a single run? If so, that might be a good
topic for an FAQ entry/blog post?
Regards
ap
