uranusjr commented on PR #71704: URL: https://github.com/apache/airflow/pull/71704#issuecomment-5328416152
I would prefer if the scheduler simply use iteration count to expire cache; using a timer there does not really make sense. Actually, should this be split into two PRs entirely? The API and scheduler changes are logically separate entirely. The API already has caching configurations, and we should fix their behavior and backport the changes in a patch version. The scheduler is _gaining_ a cache and related configurations, on the other hand, and it shouldn’t be conflated with the API changes. Those belong in a minor version instead. And the caching mechanism can be entirely different (tick-based) from the API’s. -- 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]
