Re: Consider using stale bot for issues

2020-09-17 Thread Elad Kalif
After reviewing some issues I think we might need a few more labels like: area:scheduling options missing information can't reproduce maybe we can create a dedicated slack channel to work on the small details. Elad On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik wrote: > @paola - Unfortunately the

Re: [Meeting Notes] Airflow 2.0 Dev Call #4 - 14 Sep 2020

2020-09-17 Thread Jarek Potiuk
I think there was one point at the last meeting that we have not discussed as we had no time - the documentation. I have some input to the discussion so I thought I share it here before the next one. I believe we ended up of "we have to think and review what to improve". I personally think we have

Re: [DISCUSS] Refactoring Import Errors

2020-09-17 Thread Jarek Potiuk
True Kamil. We can do it now and the file vs. dag is an important difference indeed! J On Thu, Sep 17, 2020 at 10:44 AM Kamil Breguła wrote: > Only in some cases, we do not have a DAG ID, but only have the path to the > file. > > In my opinion, we can do it now. One of the most important chan

Re: [DISCUSS] Refactoring Import Errors

2020-09-17 Thread Kamil Breguła
Only in some cases, we do not have a DAG ID, but only have the path to the file. In my opinion, we can do it now. One of the most important changes is to ensure a stable ID. Now we delete and add the errors again, and we should check which errors should be deleted and which should be added. If we

Re: [DISCUSS] Refactoring Import Errors

2020-09-17 Thread Jarek Potiuk
I am all for it. This should be - likely - connected with the future versioning of DAGs (currently deferred to 2.1). https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-36+DAG+Versioning - possibly, rather than being a separate AIP, it should be incorporated there. I believe in the versioning