I agree with whatever decision comes out of this conversation going forward.
I personally think the below option is the best given the fact that we
might be doing Airflow 3 with a certain theme in mind:
*only implement multi-team as an Airflow 3 feature (which might be
mucheasier to do -
Just to clarify the state for that one.
I would like to put that one on-hold until we get clarity on Airflow 2 vs
Airflow 3 approach:
https://lists.apache.org/thread/3chvg9964zvh15mtrbl073f4oj3nlzp2
There is currently a veto from Ash, so until it is withdrawn or we change
the problematic "team"
+1 (non-binding). Looking forward to this one.
Shubham
On 2024-04-22, 12:31 AM, "Amogh Desai" mailto:amoghdesai@gmail.com>> wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
+1 binding.
Excited to see this happen!
Thanks & Regards,
Amogh Desai
On Sat, Apr 20, 2024 at 12:11 AM Igor Kholopov
wrote:
> +1 (non-binding)
>
> Great to see this happening, hope we will see more proposals towards making
> Airflow more flexible!
>
> Regards,
> Igor
>
> On Fri, Apr 19, 2024
+1 (non-binding)
Great to see this happening, hope we will see more proposals towards making
Airflow more flexible!
Regards,
Igor
On Fri, Apr 19, 2024 at 8:10 PM Daniel Standish
wrote:
> >
> > It doesn’t affect my vote on the API, but I am very strongly against this
> > one part of the AIP:
>
>
> 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 `:` 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
+1 (non-binding)
Nice to see it moving along!
From: Ash Berlin-Taylor
Sent: Friday, April 19, 2024 9:00:42 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] AIP-67 Multi-team deployment
of Airflow components
CAUTION: This email
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 `:` 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,
To: dev@airflow.apache.org
> Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] AIP-67 Multi-team
> deployment of Airflow components
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and kn
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] AIP-67 Multi-team
> deployment of Airflow components
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
This is exciting. +1 binding.
- ferruzzi
From: Oliveira, Niko
Sent: Thursday, April 18, 2024 9:16 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] AIP-67 Multi-team deployment
of Airflow components
CAUTION: This email
+1 binding
Excited for this one!
From: Aritra Basu
Sent: Thursday, April 18, 2024 7:37:08 AM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] AIP-67 Multi-team deployment
of Airflow components
CAUTION: This email originated from
+1 (non-binding)
--
Regards,
Aritra Basu
On Thu, Apr 18, 2024, 7:42 PM Bishundeo, Rajeshwar
wrote:
> +1 (non-binding)
>
> -- Rajesh
>
>
>
>
>
>
> On 2024-04-18, 10:11 AM, "Vincent Beck" vincb...@apache.org>> wrote:
>
>
> CAUTION: This email originated from outside of the organization. Do not
+1 (non-binding)
-- Rajesh
On 2024-04-18, 10:11 AM, "Vincent Beck" mailto:vincb...@apache.org>> wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
+1 binding
On 2024/04/18 11:10:32 Jarek Potiuk 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:
>
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:
16 matches
Mail list logo
