[GitHub] [airflow] potiuk commented on issue #20475: Custom Timetable error with CeleryExecutor

[GitBox <gi...@apache.org>]

potiuk commented on issue #20475:
URL: https://github.com/apache/airflow/issues/20475#issuecomment-1000269635


   I looked at it and seems this is simply triggerered by `get_templatae_context()` in file_handker - it tries to retrieve all context (including the deprecated `next_ds` > `get_next_execution_date` -> `following_schedule` -> `infer_automated_data_interval`) and that triggers the exception. 
   
   I'd say we should simply set the `next_ds` to be some value (might be None possibly ) but we should not raise the exception, because this will always happen with any custom timetable not deriving from one of "our" built-in timetables.
   
   Did I get it right @uranusjr ?
   
   @lionheart106008 -> I think what would be good workaround for you to derive your timetable from `NullTimetable` - this should make the `next_ds` equal to `logical_date`. This likely makes little sense for your case, but `next_ds` field is deprecated so you should not use it anyway (and you don't) in your DAG - but at least it will not crate. 
   
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org