Re: [DISCUSS] Common.util provider?

2024-04-11 Thread Jarek Potiuk
want to point out is, for the provider to actually be helpful, it >>> must >>> >> be >>> >>> treated a bit differently from normal providers, but more like a >>> separate >>> >>> third-party dependency. Specifically, the prov

Re: [DISCUSS] Common.util provider?

2024-03-10 Thread Jarek Potiuk
Dr. Markus Heyn, Dr. Frank Meyer, >> Dr. >> >>>>> Tanja Rückert >> >>>>> >> >>>>> -Original Message- >> >>>>> From: Jarek Potiuk >> >>>>> Sent: Mittwoch, 21. Februar 2024 21:

Re: [DISCUSS] Common.util provider?

2024-02-22 Thread Jarek Potiuk
ntially > >>> more difficult to maintain, so I’d settle for one utility provider for > >> now > >>> and split further if needed in the future. > >>> > >>> TP > >>> > >>> > >>>> On 22 Feb 2024, at 10:10, Scheffler Jens (XC-

Re: [DISCUSS] Common.util provider?

2024-02-22 Thread Tzu-ping Chung
;>> @Uranusjr would this help as a pilot in your AIP-60 code to parse and >>> validate URIs for datasets? >>>> >>>> Mit freundlichen Grüßen / Best regards >>>> >>>> Jens Scheffler >>>> >>>> Alliance: Enabler

Re: [DISCUSS] Common.util provider?

2024-02-22 Thread Maciej Obuchowski
/EAE-ADA-T) > > > Robert Bosch GmbH | Hessbruehlstraße 21 | 70565 Stuttgart-Vaihingen | > > GERMANY | www.bosch.com > > > Tel. +49 711 811-91508 | Mobil +49 160 90417410 | > > jens.scheff...@de.bosch.com > > > > > > Sitz: Stuttgart, Registergericht: Amtsge

Re: [DISCUSS] Common.util provider?

2024-02-22 Thread Jarek Potiuk
ratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; > > Geschäftsführung: Dr. Stefan Hartung, Dr. Christian Fischer, Dr. Markus > Forschner, > > Stefan Grosch, Dr. Markus Heyn, Dr. Frank Meyer, Dr. Tanja Rückert > > > > -Original Message- > > From: Jarek

Re: [DISCUSS] Common.util provider?

2024-02-21 Thread Tzu-ping Chung
Dr. Stefan Hartung, Dr. Christian Fischer, Dr. Markus > Forschner, > Stefan Grosch, Dr. Markus Heyn, Dr. Frank Meyer, Dr. Tanja Rückert > > -Original Message- > From: Jarek Potiuk > Sent: Donnerstag, 22. Februar 2024 00:53 > To: dev@airflow.apache.org > Subject: R

RE: [DISCUSS] Common.util provider?

2024-02-21 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
, Stefan Grosch, Dr. Markus Heyn, Dr. Frank Meyer, Dr. Tanja Rückert -Original Message- From: Jarek Potiuk Sent: Donnerstag, 22. Februar 2024 00:53 To: dev@airflow.apache.org Subject: Re: [DISCUSS] Common.util provider? Yep. It could work with symbolic links. Tested it and with flit - both

Re: [DISCUSS] Common.util provider?

2024-02-21 Thread Jarek Potiuk
//eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F > > aka.ms%2Fo0ukef=05%7C02%7CJens.Scheffler%40de.bosch.com%7C98c8897 > > 195d944d483ab08dc331a49bb%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7 > > C638441435197193656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj > >

RE: [DISCUSS] Common.util provider?

2024-02-21 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
Markus Forschner, Stefan Grosch, Dr. Markus Heyn, Dr. Frank Meyer, Dr. Tanja Rückert -Original Message- From: Jarek Potiuk Sent: Mittwoch, 21. Februar 2024 21:18 To: dev@airflow.apache.org Subject: Re: [DISCUSS] Common.util provider? > if we have a common piece then we are locking all

Re: [DISCUSS] Common.util provider?

2024-02-21 Thread Jarek Potiuk
a single > place but keep individual providers fully independent… > > Jens > > Sent from Outlook for iOS<https://aka.ms/o0ukef> > > From: Jarek Potiuk > Sent: Wednesday, February 21, 2024 5:42:20 PM > To: dev@airflow.apache.org > Sub

Re: [DISCUSS] Common.util provider?

2024-02-21 Thread Scheffler Jens (XC-AS/EAE-ADA-T)
… Jens Sent from Outlook for iOS<https://aka.ms/o0ukef> From: Jarek Potiuk Sent: Wednesday, February 21, 2024 5:42:20 PM To: dev@airflow.apache.org Subject: [DISCUSS] Common.util provider? Hello everyone, How do we feel about introducing a common.util pr

[DISCUSS] Common.util provider?

2024-02-21 Thread Jarek Potiuk
Hello everyone, How do we feel about introducing a common.util provider? I know it's not been the original idea behind providers, but - after testing common.sql and now also having common.io, seems like more and more we would like to extract some common code that we would like providers to use,