hitepages.com>
> > > wrote:
> > >
> > >> What I am doing is very similar. However I am including the DagRun's
> id
> > in
> > >> the pool name to make it unique, as I need to make sure every run gets
> > its
> > >> own pool. I am getti
te methods or templates. How do you make sure each
> >> run has it's own pool?
> >>
> >>
> >> Thanks,
> >>
> >> Dávid Szakállas
> >> Software Engineer | Whitepages Data Services
> >>
> >>
>
un has it's own pool?
>
>
> Thanks,
>
> Dávid Szakállas
> Software Engineer | Whitepages Data Services
>
>
> From: Taylor Edmiston
> Sent: Thursday, September 20, 2018 6:17:05 PM
> To: dev@airflow.incubator.apache.org
> Subject
has it's own pool?
Thanks,
Dávid Szakállas
Software Engineer | Whitepages Data Services
From: Taylor Edmiston
Sent: Thursday, September 20, 2018 6:17:05 PM
To: dev@airflow.incubator.apache.org
Subject: Re: Creating dynamic pool from task
I've done something
I've done something similar. I have a task at the front of the DAG that
ensures the connection pool exists and creates the pool if it doesn't.
I've pasted my code below. This runs in a for loop that creates one DAG
per iteration each with its own pool. Then I pass the pool name into the
