On Wed, Jun 26, 2019 at 9:45 PM Gerard Toonstra wrote:
>
> That's not my experience of how SLA's work at the moment. I've observed
> this to currrently work as:
>
> 1. An SLA is configured as the "time delta" after some dag execution
> schedule.
>
That's not my experience of how SLA's work at the moment. I've observed
this to currrently work as:
1. An SLA is configured as the "time delta" after some dag execution
schedule.
2. The SLA is configured at task level, so any tasks still running or need
to run after "time delta" will be aggregated
or working with SQL Server.
> Obiously you need to install the tools in airflow workers.
>
> Cheers,
> Philip
>
> El 31-05-2019, a la(s) 09:57, Gerard Toonstra
> escribió:
>
> > Hi all,
> >
> > We're running airflow and write data to sqlserver. Python a
Hi all,
We're running airflow and write data to sqlserver. Python and sqlserver
isn't a marriage made in heaven and we've literally spent hours fixing
driver issues, installations and working around things that should be easy,
time that's better spent writing app code.
I looked at Sqoop, but that
This sounds interesting. I set up the site "ETL with airflow" ages ago and
it's still getting daily forks / stars on github.
I'm not a tech writer, but have good experience writing documentation and
would like to learn about the scope and objectives
and what the docs have to cover that's not alrea
