It doesn’t affect my vote on the API, but I am very strongly against this one part of the AIP:
> … dag_id are namespaced with `<team>:` prefix. This specific part is getting an implementation/code veto from me. We made the mistake of overloading one column to store multiple things in Airflow before, and I’ve dealt with the fallout in other apps in the past. Trust me: do. not. do. this. > On 18 Apr 2024, at 12:10, Jarek Potiuk <ja...@potiuk.com> wrote: > > Hello here. > > I have not not heard a lot of feedback after my last update, so let me > start a vote, hoping that the last changes proposed addressed most of the > concerns. > > Just to recap. the proposal is here: > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-team+deployment+of+Airflow+components > > Summarizing the most recent changes - responding to comments and doubts > raised during the discussion: > > * renamed it to be multi-team to clarify that this is the only case it > addresses > * splitting it into two phases: without and with internal API AIP-44 (also > named as GRPC server) > * implifying the approach for Variables and Connections, where no changes > in Airflow will be needed to handle the DB updates. > > This makes phase 1 simpler and not depending on AIP-44. > > The vote will last till next Friday 26th of April 2024 Noon CEST. > > J.
