Re: How to know the DAG is starting to run
Okay I’ll bite... WT* does that mean?
one of the best things about airflow is how easy it is to connect disparate systems... some would even say that’s much of the reason it exists..
It records reasonable metadata into an rdms (I suppose you could argue for other designs, but it’s pretty straightforward and for this workload easy enough to scale).
So... what did you mean?
Sent from a device with less than stellar autocorrect
> On May 11, 2018, at 7:19 AM, Luke Diment <Luke.Diment@xxxxxxxxxxxxx> wrote:
> We should really instrument an interface for airflow so integration is more succinct between disparate systems!!!
> Sent from my iPhone
>> On 12/05/2018, at 12:09 AM, James Meickle <jmeickle@xxxxxxxxxxxxxx> wrote:
>> You can put an operator as the very first node in the DAG, and have
>> everything else in the DAG depend on it. For example, this is the approach
>> we use to only execute DAG tasks on stock market trading days.
>> -James M.
>>> On Fri, May 11, 2018 at 3:57 AM, Song Liu <songliu@xxxxxxxxxxx> wrote:
>>> I have something just want to be done only once when DAG is constructed,
>>> but it seems that DAG will be instanced every time when run each of
>>> So is that there function in DAG that tell us it is starting to run now ?
> The contents of this email and any attachments are confidential and may be legally privileged. If you are not the intended recipient please advise the sender immediately and delete the email and attachments. Any use, dissemination, reproduction or distribution of this email and any attachments by anyone other than the intended recipient is prohibited.