potiuk commented on PR #41730: URL: https://github.com/apache/airflow/pull/41730#issuecomment-2331206674
> How much pressure do you feel to remove AIP-44? I personaly don't feel much pressure - other than all the "peer" presure where other deprecations being actively removed as we speak. Also I am going for almost 3 weeks holidays after the Summit, so it's less for me and more for all the work that is going to happen around AIP-72 especially while I am away. There is quite some overlap - a lot of code for AIP-72 is going to involve refactorings and rewrites of pretty much the same parts as AIP-44 touched - it will be on a higher level than AIP-44 did (becasue while AIP-44 went very "low level" - and replaced and extracted individual DB transactions from the code, AIP-72 is going to implement a way higher "abstraction" as regular API calls, where the operations - task and daf file parsing, and callbacks - will be wrapped in higher-level API calls. But I imagine a lot of the code/ implementation will be about pretty much the same code (and your concerns about Edge worker switching to using the APIs of AIP-72 are only confirming that) I thought that removing AIP-44 code first (and keeping tests running) would remove quite a lot of noise from AIP-72 work, so I think it might be worth doing before. But ultimately, it's up to @ashb POC (which we have not seen yet) and details how the implementation of AIP-72 will be done (Replace? Copy? Running old DB functionality and new code in parallel? Duplicating the code first in separate projects before proceeding with AIP-72 implementation). So I think the question "Should we remove AIP-44 first or is it ok to leave it for now" is more a question on how AIP-72 process will look like - and as such only @ashb can answer it properly I think. -- 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]
