Ferdinanddb commented on issue #58056:
URL: https://github.com/apache/airflow/issues/58056#issuecomment-3564911960

   Thanks for taking the time to propose a draft! I think it looks good with 
regard to how the Asset behaves currently, in my humble opinion.
   
   Something that I tried to express in the issue's description is that, given 
my use case, it would be so nice if the Asset(s) and the CRON expression are 
"matching" in the sense that a CRON expression is defined by its datetime value 
(very restrictive) while an Asset does not follow the same rules. For example, 
a parent DAG having a  logical date value being 2 years ago can generate an 
Asset event which would consumed by the child DAG no matter what. It would be 
so nice if the child DAG could be triggered only if the CRON expression is 
matched, and the Asset(s) it is waiting for have been generated by DAGs having 
a similar logical_date value.
   
   I hope I am clear and I know this is a bit convoluted, but this would be so 
nice to have. I guess such a thing would require to change the logic of the 
Asset object consumption somehow.
   
   That being said, thank you very much for the proposal, and I guess your 
proposal makes sense given how Asset objects are working as of now!


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