SamWheating commented on issue #18816:
URL: https://github.com/apache/airflow/issues/18816#issuecomment-938180613
Oh cool, I hadn't seen that discussion. Thanks for sharing!
It sounds like the larger backfill redesign is a much larger feature which
will likely require its own AIP in order to gather requirements and feedback
from the community, correct? I will think about some requirements and evaluate
how much capacity I have to get involved with a larger change.
In the short term, I think it wouldn't be too difficult to expose the
existing CLI-based backfill functionality in the REST API, but I acknowledge
that this comes with some downsides:
- Since Backfills aren't really their own entity / model in Airflow it
would be difficult to implement any read/update/delete operations on them.
- Anything we change now would likely need to be refactored when a larger
redesign of backfills takes place.
What do you think, is it worth proceeding with a near-term fix or should any
changes to the backfill functionality be grouped together as part of a larger
AIP?
--
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]
