Re: [VOTE] Release Apache Airflow Helm Chart 1.6.0 based on 1.6.0rc2

2022-05-18 Thread Jarek Potiuk
+1 (binding) - checked sigs/sums/licences, run it locally. Additionally I can confirm Helm + Airflow 2.3.0 works natively (I.e. FAST) on ARM platform (postgres) without any modifications of the chart or image. Not a prerequisite as ARM is still experimental, but it seems to work without any problem

Re: Missing "start_date" or why must a DAG have one

2022-05-18 Thread Malthe
On Wed, 18 May 2022 at 17:18, Ash Berlin-Taylor wrote: > Start date also makes sense for a cron-based dag with catch-up too though... True. So, 1. A timedelta without a `start_date` is not wrong, but it'll use midnight as the reference time (I think this is better than "date first added" becaus

Re: Missing "start_date" or why must a DAG have one

2022-05-18 Thread Ash Berlin-Taylor
Start date also makes sense for a cron-based dag with catch-up too though... On 18 May 2022 16:58:54 BST, Malthe wrote: >On Sat, 14 May 2022 at 11:21, Bas Harenslak wrote: >> I think we have the following options when no start_date is given: >> >> 1. schedule_interval is alias e.g. “@daily” —>

Re: [DISCUSSION] AIP-49 OpenTelemetry Support for Apache Airflow

2022-05-18 Thread Howard Yoo
Hi Malthe, 1. You are right - those were merely added to those 'counter' metrics to see if populating helpful attributes alongside of them would be feasible and also helpful or not - and does not represent the final form of the implementation. I would hope the actual implementation of this proposa

Re: Missing "start_date" or why must a DAG have one

2022-05-18 Thread Malthe
On Sat, 14 May 2022 at 11:21, Bas Harenslak wrote: > I think we have the following options when no start_date is given: > > 1. schedule_interval is alias e.g. “@daily” —> is a cron expression > internally (0 0 * * *), so run at 00:00 > 2. schedule_interval is cron e.g. “0 0 * * *” —> cron exp

Re: [DISCUSSION] AIP-49 OpenTelemetry Support for Apache Airflow

2022-05-18 Thread Malthe
On Fri, 25 Mar 2022 at 20:40, Howard Yoo wrote: > I am pleased to announce the start of the discussion for the new AIP draft > that was recently been published: > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-49+OpenTelemetry+Support+for+Apache+Airflow Some comments: 1. The optional

Re: [DISCUSS] Approach for new providers of the community

2022-05-18 Thread Jarek Potiuk
Hello everyone, I think we have a series of things that make it difficult to focus on such long term discussions - 2.3.0 was out, many people are busy with 2.3.1 which is going to focus on "teething" problems and we have Airflow Summit next week (yay!) and I know how many people in our communit