I’ve written some code to generate dags from yaml.. would be interested in
collaborating
> On Oct 1, 2018, at 7:43 PM, 김용휘 wrote:
>
> I respects you plan.
> so I would like to join in collaborating.
>
> What can I do for this?
>
>
> -Original Message-
> From: "siddharth gupta"
>
I respects you plan.
so I would like to join in collaborating.
What can I do for this?
-Original Message-
From: "siddharth gupta"
To: ;
Cc:
Sent: 2018-10-02 (화) 09:37:54
Subject: Looking for collaborators
Hello Folks!
I am working on an Airflow Plugin to auto generate DAG code
Hello Folks!
I am working on an Airflow Plugin to auto generate DAG code from the UI and
YAML (already have initial design on how it can work etc). I am looking for
folks interested in collaborating. Please reach out to me if you are
interested :)
You can reach out to me at sid8...@gmail.com
Changing terms or aliasing may both introduce another set of confusions.
Refining the documentation systematically may be a more feasible solution
to this sort of issues? Like having “execution_date” in “Concepts” section,
or having a dedicated section named “Vocabularies” to list all potentially
The champion need not be the one to do all of this. Anyone from the PPMC
can help with the task list. One point to add to Jakob's list (given the
general popularity of Airflow) is the press release to announce Airflow as
a TLP as soon as the board approves the resolution. This will require some
Hi
I am coding various data flows and one of the requirements we have is to
have some error tasks happen when some of the tasks failure. These error
tasks are specific to the task that failed and are not a generic to the
whole DAG
So for instance if I have a DAG that runs the following
Mentors, kindly sign-off!
https://wiki.apache.org/incubator/October2018#preview
I'm not against aliasing personally.
The downside is that it creates more vocabulary overall and most users will
need to learn the mapping of the given aliases at some point in their
learning curve anyways. Only users in environments free of `execution_date`
will benefit from less confusion, and
Very good slides indeed. It's fast-forward over concept of Airflow that
everyone new should follow.
Maybe that could be a base for a short (interactive ?) tutorial for someone
who would like to learn more about Airflow. I think there are few concepts
which are not obvious (recently discussed
