, August 20, 2024 10:05 PM
To: dev@airflow.apache.org
Subject: RE: [EXT] [VOTE] New Provider for Core operators/sensor
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.
AVERT
1. Provider name
+1 for standard, core
+0.5 for essential/s - it gives me a sense that it is mandatory
-1 for common, shared, builtin, primary
2. -1 for placing under common
Thanks & Regards,
Amogh Desai
On Wed, Aug 21, 2024 at 2:10 AM Pankaj Singh
wrote:
> +1 core
> The implementation of cer
+1 core
The implementation of certain operators and sensors, such as
TriggerDagRunOperator, ExternalTaskSensor, relies on the core module in a
way, so it makes sense to have the apache-airflow-providers-core for them.
We may keep other operators such as python, bash here.
+1 (common.time)
There ar
-1 on common as well, +1 to standard/essentials (non-binding)
--
Regards,
Aritra Basu
On Tue, 20 Aug 2024, 5:03 pm Elad Kalif, wrote:
> > IMHO this vote is about a code change
>
> Then we will consider PMCs -1 as veto which disqualifies the specific name.
> Looks like standard is the leading opt
> IMHO this vote is about a code change
Then we will consider PMCs -1 as veto which disqualifies the specific name.
Looks like standard is the leading option which got enough +1 and no
vetos but lets see how it proceeds till vote time is closed.
On Tue, Aug 20, 2024 at 2:11 PM Hussein Awala wrot
> Hussein I believe the intent is that the provider comes as one unit with
Airflow (it will be part of the pre-installed providers like: sqlite, HTTP,
...) so in that spirit is essential.
What about installing Airflow 3 by default without any provider (minimal
version), and adding the current defa
+1 binding on essential/essentials, standard, builtin, primary,
- 0 binding on core, shared, base
-1 binding on common path
On Tue, Aug 20, 2024 at 12:45 AM Ephraim Anierobi
wrote:
> +1 standard
> +0 essential/essentials (makes it seem required)
>
> If it were available, I would have chosen t
+1 standard
+0 essential/essentials (makes it seem required)
If it were available, I would have chosen the "core-add-on" option. It
gives the feeling that it's a provider that complements the
core(apache-airflow-providers-core-add-on).
- 1 under common
On Mon, 19 Aug 2024 at 22:12, Elad Kalif w
Hussein I believe the intent is that the provider comes as one unit with
Airflow (it will be part of the pre-installed providers like: sqlite, http,
...)
so in that spirit is essential.
just to clarify PMC voting -1 is considered veto but the rule is applied to
code change, I am not sure what it m
1. I'd like to cast my votes as follows:
-1: "builtin", "primary", "core", "base" - all confuse between Airflow's
real core and the new provider.
-1: "shared "- a "common" synonym, there's no point to rename it in this
case.
+0: "essential(s)" - it distinguishes the new provider from Airflow's c
-1 on common (I explained why in the discuss thread)
+1 standard
+0 builtin
-0 primary
+1 core
-0 base
-1 shared (same as common)
-1 on essential/s (by definition, essential is a thing that is absolutely
necessary, which is not the case here, a lot of users use Airflow without
the core operators/se
Easy one first: -1 on common
+1 on standard, but also +0.5 on core or essential too.
+1 essentials (plural is better IMHO) (great suggestion Pavankumar!)
-1 nested under common
binding
- ferruzzi
From: Vishnu Chilukoori
Sent: Monday, August 19, 2024 7:28 AM
To: dev@airflow.apache.org
Subject: RE: [EXT] [VOTE] New Provider for Core operators
+1 standard & core -- can't pick one!
-1 under common
On Mon, 19 Aug 2024 at 15:29, Vishnu Chilukoori
wrote:
> +1 essential or essentials
> -1 under common
> (non-binding)
>
>
> --
> Regards,
> Vishnu
>
> On Mon, Aug 19, 2024 at 7:12 AM Wei Lee wrote:
>
> > Same here.
> >
> > 1. +1 essential/es
+1 essential or essentials
-1 under common
(non-binding)
--
Regards,
Vishnu
On Mon, Aug 19, 2024 at 7:12 AM Wei Lee wrote:
> Same here.
>
> 1. +1 essential/essentials
> 2. -1 under common
>
> Best,
> Wei
>
> > On Aug 19, 2024, at 9:54 PM, Bas Harenslak
> wrote:
> >
> > +1 for essential (saves
Same here.
1. +1 essential/essentials
2. -1 under common
Best,
Wei
> On Aug 19, 2024, at 9:54 PM, Bas Harenslak wrote:
>
> +1 for essential (saves one letter)
> -1 under common (feels like that would lead to path convention confusion)
>
> Bas
>
>> On 19 Aug 2024, at 15:40, Vincent Beck wrot
+1 for essential (saves one letter)
-1 under common (feels like that would lead to path convention confusion)
Bas
> On 19 Aug 2024, at 15:40, Vincent Beck wrote:
>
> Same here,
>
> +1 essential/essentials
> -1 under common
>
> Binding
>
> On 2024/08/19 13:38:38 Pavankumar Gopidesu wrote:
>>
Same here,
+1 essential/essentials
-1 under common
Binding
On 2024/08/19 13:38:38 Pavankumar Gopidesu wrote:
> Yes, I agree with Jarek :)
>
> +1 essential or essentials
> -1 under common
> (non-binding)
>
> Regards,
> Pavan
>
> On Mon, Aug 19, 2024 at 2:32 PM Jarek Potiuk wrote:
>
> > +1 es
Yes, I agree with Jarek :)
+1 essential or essentials
-1 under common
(non-binding)
Regards,
Pavan
On Mon, Aug 19, 2024 at 2:32 PM Jarek Potiuk wrote:
> +1 essential (or essentials)
> -1 under common
>
> (binding)
>
> Sorry for a bit of modification here, but I think
> `apache-airflow-provider
+1 essential/essentials
-1 under common
Same as Jarek, no opinion on plurality
On 19 August 2024 14:32:01 BST, Jarek Potiuk wrote:
>+1 essential (or essentials)
>-1 under common
>
>(binding)
>
>Sorry for a bit of modification here, but I think
>`apache-airflow-providers-essentials` (with `s` at
+1 essential (or essentials)
-1 under common
(binding)
Sorry for a bit of modification here, but I think
`apache-airflow-providers-essentials` (with `s` at the end) would be more
appropriate - showing also that it's about various "essentials". But I am
good with either. This is a nuance.
J
On
Migrate all operators/sensors from core to dedicated provider.
*Discussion thread*
https://lists.apache.org/thread/2dmlqkcmyomm4q7rrovygs6bw655zx07
This vote concerns two key decisions.
1. Provider name selection, options are:
- essential
- standard
- builtin
- primary
- core
- base
- shared
2.
22 matches
Mail list logo
