At Netflix we've put our plugin inside the DAGs folder and pointed the
config to it there so we can both import directly in DAGs AND update the
plugin as we go. This makes it easy to test changes to operators needed for
ongoing DAG development in the same PR.
The two plugin features I've used whic
It's presumably useful if you want to package your plugins for other people
to use but it seems like everyone just adds those directly to the Airflow
codebase these days.
On Thu, Mar 29, 2018 at 4:27 PM Kyle Hamlin wrote:
> Yeah so far I have only written hooks and operators so maybe the benefit
Yeah so far I have only written hooks and operators so maybe the benefit only
kicks in for other airflow abstractions.
> On Mar 29, 2018, at 7:15 PM, George Leslie-Waksman
> wrote:
>
> We also import our operators and sensors directly.
>
> However, executors and some other pieces are a littl
We also import our operators and sensors directly.
However, executors and some other pieces are a little bit harder to deal
with as non-plugins
On Thu, Mar 29, 2018 at 3:56 PM Kyle Hamlin wrote:
> Hello,
>
> I just got done writing a few plugins, and the process has left me
> wondering what the
Hello,
I just got done writing a few plugins, and the process has left me
wondering what the real benefits are? As far as I can tell, it makes
testing more difficult since you cannot import from the created module, you
have to import directly from the plugin. Additionally, your code editor
isn't a
And thx to the mentors (Hitesh and Jakob) for signing off so quickly!
-s
On Thu, Mar 29, 2018 at 10:39 AM, Chris Riccomini
wrote:
> Thanks, Sid!
>
> On Wed, Mar 28, 2018 at 11:08 PM, Sid Anand wrote:
>
> > FYI!
> > I filled out the podling report due in April.
> >
> > https://wiki.apache.org/in
Thanks, Sid!
On Wed, Mar 28, 2018 at 11:08 PM, Sid Anand wrote:
> FYI!
> I filled out the podling report due in April.
>
> https://wiki.apache.org/incubator/April2018
>
> Mentors, please don't forget to sign-off!!
>
> -s
>
> On Wed, Mar 28, 2018 at 3:19 AM, wrote:
>
> > Dear podling,
> >
> > Th
(Creating a new thread)
Hi Max,
I was just wondering about this. There are definite use cases for people
having only view access to some DAGs, mostly for monitoring. I want to know
what the upstream DAGs are doing, but maybe I don't need clear/run access.
I feel like the granular operation permi
Hijacking the thread further here, any thoughts on how to breakdown per DAG
access?
Tao & I are talking about introducing per-DAG permissions and one big
question is whether we'll need to support different operation-types at a
per-DAG level, which changes the way we need to model the perms.
First
Yes, the idea was to eventually serve and develop the local community by
providing a meet-up of their own.
-s
On Thu, Mar 29, 2018 at 3:21 AM, Sumit Maheshwari
wrote:
> Hi Sid,
>
> All these meet-up locations are quite far for someone in Bangalore, who
> would like to attend. Also due to timezon
Hi Sid,
All these meet-up locations are quite far for someone in Bangalore, who
would like to attend. Also due to timezone differences, live streaming is
also not very useful.
However, I've got only a few responses so far, so maybe it's not the time
to host a meetup in Bangalore. Will see how man
11 matches
Mail list logo
