You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/06/10 14:27:25 UTC

[GitHub] [airflow] uranusjr commented on pull request #16352: DagRun.date_interval_start and date_interval_start

uranusjr commented on pull request #16352:
URL: https://github.com/apache/airflow/pull/16352#issuecomment-858670073


   > Oh, we'll need to add these to the OpenAPI defn too.
   
   Yeah, I’m working on it, the `post_dag_run` endpoint also needs updating. How should we handle backward compatibility in API? My current approach is to allow the caller to pass *either* `execution_date` or `data_interval_[start|end]`, but how do I make this show in the schema? Also, is there a way to emit a message to tell the client to migrate?


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

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