I like "essential" - how about "apache-airflow-provider-essentials" - that
will not limit it to only operators, we could add mixins, triggers, hooks
(BaseHook) and everything else that falls into "essentials" category.
On Sat, Aug 17, 2024 at 2:43 AM Pavankumar Gopidesu
wrote:
> Also like core,
While I think "system" tests use case is indeed - as Daniel wrote - not a
good reason, I find it intriguing as a "commenting out" things from DAG.
Sounds like a useful authoring feature to have a "never" trigger rule.
The "callable" use case is likely a bit too much - we've been discussing
"flexib
Yeah, I think essential sounds pretty good as well. Good suggestion Pavan
--
Regards,
Aritra Basu
On Mon, 19 Aug 2024, 3:09 am Jarek Potiuk, wrote:
> I like "essential" - how about "apache-airflow-provider-essentials" - that
> will not limit it to only operators, we could add mixins, triggers,
On 2024/07/16 17:03:40 Vikram Koka wrote:
> Thank you all.
> I believe that this is an important foundational improvement for Airflow
> and really appreciate your support in moving this forward.
>
> Vikram
>
>
> On Tue, Jul 16, 2024 at 7:34 AM Ash Berlin-Taylor wrote:
>
> > This vote has passed
https://lists.apache.org/thread/wnt3pxt3xxgw3fw4vdscd2wkfl13829z
Hi Team,
Replying to this email thread from Teradata Provider,
To provide some context on how the Teradata providers dashboard functions:
1. Execute Teradata system tests using the command `pytest --system=teradata
--junitxml=rep
