jscheffl commented on issue #37810: URL: https://github.com/apache/airflow/issues/37810#issuecomment-1984323146
> With that established, if we store extra metadata (of a dataset), it only makes sense to allow extra metadata also when an XCom is written. But if we use XCom for the extra, writing to XCom would write… extra metadata to XCom? And does that extra metadata also has a dataset URI and can have extra extra metadata? It becomes awkward. I would see it as "we use existing XCom meta data" but not add new one. The data is just copied to the next DAGrun Conf on top. What therefore comes into my mind: We could also add a flag to the `outlet` parameter - as `extra` is optional and if specified is static, we could set another marker if task return value (==XCom) shall be taken over as `extra`event data. Otherwise just no data is taken over as default. -- 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]
