After all the exploration of this topic here in this thread, I'm a pretty
hard -1 on this one.
I think CWL and CWL-Airflow are great projects, but they can't rely on the
Airflow community to evolve/maintain/package this integration.
Personally I think that generally and *within reason* (winking
I looked at the
> https://cwl-airflow.readthedocs.io/en/1.0.18/readme/how_it_works.html#what-s-inside
> to
> understand what CWL is and that's where I took the descriptor + job (in Key
> Concepts).
>
Oh this is an old one, but even new one probably does not reflect the real
picture.
OK.
Yes Fokko that is true, the overall aggregated saving from removing the
overhead is actually gonna be esp. large for us as we start tens of
millions of tasks everyday. Looking forward to include that change in our
code base.
Hi Jarek, automated performance testing sounds extremely tasty and we
Happy to help with the NA event organization too, if it happens in Bay Area.
Cheers,
Kevin Y
On Tue, Nov 12, 2019 at 1:12 PM Austin Bennett
wrote:
> As an airflow user, and based in Bay Area (proposed first location), with
> experience organizing events -- happy to contribute.
>
> On Tue, Nov
>
> I hope ideas in that treads and questions do not interfere with current
> discussions. I have not mentioned anything about `cwl descriptor + job`
> (Michael K probably did :(), but in current implementation CWL Description
> is static and lives long live :) and then one can attach a sensor to
On Thu, Nov 14, 2019 at 2:58 AM Andrey Kartashov wrote:
> I'm sorry I have not used quotes. But now, I do not understand at all what
> we are discussing. The email system mixed time and order. Can we all have a
> phone/skype/hangouts/jeet.si call where we can quickly reduce the problem
> and
